On 2020-08-14 10:29, Greg Ercolano wrote:
> 	My thinking of the optimal layout would be:
> 
> 		<build>/bin      <-- fluid (wrapper on OSX) and fltk-config would go here
> 		<build>/examples <-- example execs (mixed with some cmake cruft might be OK)
> 		<build>/test     <-- test execs (mixed with some cmake cruft might be OK)

    Also: I think keeping fltk-config and fluid in a separate bin dir would help
    motivate developers to add <build>/bin to their own Makefile PATH's so as to
    reach those tools, and those tools alone, without accidentally picking up all
    the other test + example executables in their build path.

    So even if we have to go with putting test + examples in the same dir, perhaps
    it would be useful to be kept separate from the fltk-config + fluid bin dir.

-- 
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/4987dd20-ed5f-a8fd-e541-b5be5a7ce1f3%40seriss.com.