I still don't see an issue with just detecting the version of automake being used, and setting a conditional that indicates whether or not to use explicitly include the subdir. Seems like a pretty trivial solution.
On Sep 3, 2013, at 3:49 PM, "Jeff Squyres (jsquyres)" <jsquy...@cisco.com> wrote: > On Sep 3, 2013, at 6:45 PM, FabrÃcio Zimmerer Murta > <fabri...@familiamurta.org> wrote: > >> I think autotools has a concept of disallowing symlinks as it seems symlinks >> can't be done in a portable way, and the goal of autotools is making >> projects portable. >> >> Well, if the autotools user feels like using symlinks, then it must be >> expected to break portability wherever you take your autoconfiscated code >> to. A choice to the user. Maybe in the case, as the project is bound to >> specific compilers, it would not be a problem to loose portability a bit >> more by considering symbolic linking around. > > Fair enough. > > We've been using sym links in the OMPI project for years in order to compile > a series of .c files in 2 different ways. It's portable to all the places > that we need/want it. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
