I'm working on porting some of my own code to use iffe and nmake. But my code relies on other code that will not be configured using these tools. I therefore face the usual problem of figuring out what -I options have to be passed to the compiler and what -L and -l options have to be passed to the linker in order to compile my code against non-AST libraries.
Reading the documentation for iffe(1), I cannot see how iffe might help with this problem. I realize that AST itself does not have this problem because it is self-contained: nmake sees all and knows all. Does anyone have suggestions for how to use the AST tools to build something that depends on non-AST software? I hate GNU autoconf and refuse to go in that direction, but I'm hoping something in the AST suite would be better than starting from scratch. Norman _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
