DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR Pending]

Link: http://www.fltk.org/str.php?L2317
Version: 1.3-current
Fix Version: 1.3-current (r7452)


Michael Surette wrote:

> Your patch will do the job, however there is no real need to search the
> source directory, so removing that declaration is preferable.  This in
> turn necessitates reducing a few #include declarations to the canonical
> form, which isn't a bad idea in itself.

Okay, I see. I agree that changing the #include's would be good.

However, I had thought that we would need the source directory to find the
FL/ include files... well, indeed I had also seen that they are copied to
the build directory, but didn't recall it then.

In general, I would prefer *not* to copy the FL directory instead, but
currently we would need the symlinks to stay compatible. OTOH, we're
thinking of removing the links anyway, and this will probably be done
before the 1.3 release (at least we plan to make the default not to create
the links: configure --without-links).

That said, I can see three ways to go:
 (1) don't copy the FL dir at all, and don't create links
 (2) don't copy the FL dir, but create the symlinks (to the source dir)
 (3) copy the source dir and create symlinks

What we have now is (3), my preferred solution would be (1), but maybe we
should go with (2) for now. This would enable us to simply remove creating
the links in a future version. It should be an option anyway (see configure
option above).

The reason why I would like to stay with the source directory search is
that we might have more directories to search in the future (FL/, fltk/,
fltk2/, fltk3/, ...), and I don't even want to *think* of copying all
directories.

So, if you could manage to make solution (2) work, this would be my
preferred way to go. Do you see anything I didn't see, or would this (2)
be possible?


Link: http://www.fltk.org/str.php?L2317
Version: 1.3-current
Fix Version: 1.3-current (r7452)

_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to