Ralf Hemmecke <[EMAIL PROTECTED]> writes: | > | > | Look at | > | > | http://fricas.svn.sourceforge.net/viewvc/fricas/branches/aldor-interface/src/Makefile.in?view=markup | > | > | | I had to add... | > | > | | all-aldor: all-axiomsys all-algebra | > | > | cd aldor && ${MAKE} | > | > | | No? | > | > Assuming one always to build all-aldor. | > | | > | Why? I can have a target that is only used if it is mentioned in | > | @[EMAIL PROTECTED] | > | > I was under the impression that user should be given option to elect | > to build the Aldor compabitility libs, and that compatibility depends | > on the Aldor compiler being around. | | Good suggestion. Currently, there is no such choice. I simply let | building the interface start, if all the aldor parts are present. | I first have to figure out, how to add some '--enable-aldor' or | '--disable--aldor'.
AC_ARG_ENABLE is the Autoconf macro for that. See the places in configure.ac.pamphlet where we check for --enable-checking or --enable-gcl. | > In that case, I think it makes | > sense to have a configure-time option. If that is true, then whether | > all-aldor is executed must be computed somehow. The best to collect | > all Make targets computed at configure time is axiom_src_all for the | > src/ directory. | | I already do that, but not with an explicit configure option. OK. -- Gaby ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ open-axiom-devel mailing list open-axiom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
