Hello Glenn, That is exactly what I need. Many thanks - it's working now.
Alexander On Thu, 11 Nov 2010, Glenn Fowler wrote: > > this will do it > --- > .PROBE.INIT : .PROBE.FIX > > .PROBE.FIX : .MAKE .VIRTUAL .FORCE .AFTER > CC.PREFIX.ARCHIVE = > CC.SUFFIX.ARCHIVE = .lib > --- > .PROBE.INIT is in the default Makerules.mk and > is made after the user makefiles have been read > .PROBE.FIX is yours and will be made after .PROBE.INIT is made > > if you have your own global makefile it can go in there > or you can make one and run nmake like this > nmake -g your-own-global-makefile.mk ... > or put this in your makefile > include your-own-global-makefile.mk > and put ../lib/make/your-own-global-makefile.mk in a sibling > dir on $PATH (e.g., if $HOME/bin is in $PATH then name it > $HOME/lib/make/your-own-global-makefile.mk) > > or you can name a file > ../lib/make/YOUR_OWN_ASSERTION.mk > in a sibling dir on $PATH and then assert this in your makefile > :YOUR_OWN_ASSERTION: > > On Thu, 11 Nov 2010 21:30:03 +0100 (CET) Alexander Thorp wrote: > > Hello Glenn, > > > I would like to override CC.PREFIX.ARCHIVE and CC.SUFFIX.ARCHIVE since > > I have a number of existing libraries which do not use the convention > > lib$(NAME).a but rather $(NAME).lib, and I would prefer not to mix > > conventions. The probe info isn't wrong as such, since the compiler can > > accept lib$(NAME).a - it just doesn't match what I need. > > > I am cross-compiling, and did have a struggle to get probe to run > > successfully, but those problems weren't connected to this one with > > library naming conventions. > _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
