On Sep 4, 2008, at 8:50 AM, Rainer Müller wrote: > Jean-Charles VERDIE (Pleyo) wrote: > >> I'm using CMake 2.6 on OSX from MacPorts. >> When using the env. variable CMAKE_INSTALL_PREFIX, it is hard >> coded to >> "/usr/local" on UNIX systems and we fall in this category. >> It does not make sense in my opinion since MacPort roots to /opt/ >> local. >> What's the opinion on this? > > If using cmake outside of MacPorts you could accidentally write > files to > /opt/local which are out of control of MacPorts. I think /usr/local > is a > more reasonable default. Ports using cmake can still overwrite it > in the > Portfile.
Agreed. > To do this automatically we could think about a cmake portgroup I think a cmake portgroup would be great. > (maybe wait for #14553) Interesting proposal! I like it. > or support it in base as a new build.type Would that have any advantages over doing it as a portgroup, do you think? I mean, even the almighty Xcode has its support implemented as a portgroup. > as the number of ports using cmake seems to grow. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
