Matt wrote:
FLTK 1.3.0 is nearing its final release, yay!
Apart from keeping the FLTK 1.3.x branch as bug-free as possible, I
was wondering what the future of FLTK should look like. For that, I
suggest that we collect ideas for a week or two, combine those with
what we have in the STRs, and
On Jan 4, 2011, at 1:57 PM, Greg Ercolano wrote:
...
I'm thinking the examples should probably be 'public domain',
to prevent the GPL/LGPL restrictions which require 'derived works'
to be given back to the lib. I can see where pedantic interpretation
of the LGPL could prevent someone from
I used .phony in documentation/Makefile to force generation
of the doc files manually independent of (not defined)
dependencies.
I couldn't find another example in our Makefiles and wonder
whether this is standard or a GNU make extension. I could
not find it on the web. Does anybody know?
If
Michael Sweet wrote:
On Jan 4, 2011, at 1:57 PM, Greg Ercolano wrote:
...
I'm thinking the examples should probably be 'public domain',
to prevent the GPL/LGPL restrictions which require 'derived works'
to be given back to the lib. I can see where pedantic interpretation
of the LGPL could
I used .phony in documentation/Makefile to force generation
of the doc files manually independent of (not defined)
dependencies.
I couldn't find another example in our Makefiles and wonder
whether this is standard or a GNU make extension. I could
not find it on the web. Does anybody know?
I used .phony in documentation/Makefile to force generation
of the doc files manually independent of (not defined)
dependencies.
I couldn't find another example in our Makefiles and wonder
whether this is standard or a GNU make extension. I could
not find it on the web. Does anybody know?
You can probably get what you want by having a dependency on a
file that never exists:
always: noSuchFile
build always
noSuchFile:
:
# remember that ':' is a dummy command on Unix
Right. That works until some wiseguy creates a file
called noSuchFile to trip you up. Tricks
On 05.01.2011 18:28, s...@sjssoftware.com wrote:
I used .phony in documentation/Makefile to force generation
of the doc files manually independent of (not defined)
dependencies.
Albrecht, is this what you're looking for?
http://www.gnu.org/software/automake/manual/make/Phony-Targets.html
On 05.01.2011 18:45, Duncan Gibson wrote:
You can probably get what you want by having a dependency on a
file that never exists:
...
Thanks, I partially did this already (see other reply: refman.pdf).
To be sure you can always do 'make clean dist', and this ought to
work as expected.
[..]
In any case, using it should be pretty harmless. It will work
as intended if the feature is supported; if not, it will do the
right thing unless the user has a file called .phony lying
around.
Hmm, sounds good. However it's not the file .phony, but the real
target (in this case
s...@sjssoftware.com wrote:
Yes, reading more carefully I see I may have misled you. If
you only use the .PHONY label there may be problems with
non-GNU make. Try this though:
foo: .PHONY
build foo
.PHONY:
I'm pretty sure that leads GNU make to build foo no matter
what, and make's
On Jan 5, 2011, at 6:17 AM, Albrecht Schlosser wrote:
I used .phony in documentation/Makefile to force generation
of the doc files manually independent of (not defined)
dependencies.
I couldn't find another example in our Makefiles and wonder
whether this is standard or a GNU make
12 matches
Mail list logo
