I'd prefer that nmake were more NOT (not off topic) on this list
nmake is not backwards compatible with posix make
that was intentional so that from the ground up nmake could make the right
choices about each item
although the one thing nmake could not shake is the significance of <TAB>
indentation
the best way to get familiar with nmake is to start using it in the
ast-open $INSTALLROOT/src tree
immediately after the first "bin/package make" works
bin/package use
cd $INSTALLROOT/src
nmake install # builds the entire src tree *in proper order*
cd lib
nmake install # builds the entire src/lib tree *in proper order*
cd libcmd
nmake install # builds just libcmd
and especially use it if you are debugging a particular subset of ast
use just about any ast Makefile except { libast 3d ksh93 } as a boilerplate
example
the 3 mentioned aren't bad per-se but they are involved a bit more than the
rest
for project style makefiles you should be familiar with
:PACKAGE:
::
:LIBRARY:
name == value
-lfoo as prerequisite, not libfoo.a or libfoo.so or foo.dll or foo.lib
On Fri, Oct 18, 2013 at 7:05 AM, Cedric Blancher
<[email protected]>wrote:
> On 18 October 2013 08:13, Glenn Fowler <[email protected]> wrote:
> > nice catch roland -- this may also fix some spurious bootstrap failures
> I've
> > seen with other compilers
> > since Mamfiles are generated by nmake the permanent place for the fix is
> in
> > src/cmd/nmake/Makerules.mk
> > diff attached
>
> OT: Can nmake be used as POSIX make?
>
> Ced
> --
> Cedric Blancher <[email protected]>
> Institute Pasteur
>
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
