That stuff about only using gnu tools is far from the case. Re this usecase supporting multiple platforms. The reason why it doesn't help is that all the rest of your makefile has similar multiplatform problems which you have to address with ifeq and its friends and it is nastier if you have make second guessing your decisions.
Regards, Tim On 30/04/2013, Paul Smith <psm...@gnu.org> wrote: > On Tue, 2013-04-30 at 17:48 +0100, Tim Murphy wrote: >> i.e. I don't just have >> load X.dll > >> I have to supply the recipe to build it on windows: > >> X.dll: >> cl.exe /Fdo$@ .... # use microsoft's compiler > >> and on Linux >> >> X.so: >> gcc -o $@ ... # using gcc > > Actually this supports Eli's point perfectly. This is no problem. You > can just put both of those rules into your makefile, and if make defines > an extension EXT for the current platform you can use "load X.$(EXT)" > and when you're on Windows it will build one way and when you're on > Linux it will build the other way. > > However, I'm still undecided on how to handle this. I'll look at it > again shortly. > > -- You could help some brave and decent people to have access to uncensored news by making a donation at: http://www.thezimbabwean.co.uk/friends/ _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
