Re: [GRASS-dev] where is GRASS looking for these dependencies?
Thanks. That is reassuring. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Head, Graduate Faculty in Complex Adaptive Systems Science Arizona State University voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu > On Jul 22, 2016, at 2:21 PM, Glynn Clementswrote: > > > Michael Barton wrote: > >> Can someone familiar with the GRASS build system tell me where it is >> looking for the following items in the configure string when >> compiling? >> >> --with-x >> --with-cxx >> --with-opengl=aqua >> --with-python >> --with-opencl > > --with-x is built into AC_PATH_XTRA which is a standard autoconf > macro. The others originate with a LOC_ARG_WITH macro (which is a > shallow wrapper around AC_ARG_WITH). This sets the variable with_foo > to "yes" if --with-foo is used with no argument, to "no" if > --without-foo is used, to the argument if --with-foo is used with an > argument, and to the default value (the third argument of > LOC_ARG_WITH, defaulting to "no") if --without-foo isn't used. > >> Thanks. I’m trying to find out if any of these are hardwired to >> specifically look in /usr/.. for stuff. > > Not by configure.in. AC_PATH_XTRA may have some hardwired defaults, > some of the other tests use pkgconf by default. > > -- > Glynn Clements ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] where is GRASS looking for these dependencies?
Michael Barton wrote: > Can someone familiar with the GRASS build system tell me where it is > looking for the following items in the configure string when > compiling? > > --with-x > --with-cxx > --with-opengl=aqua > --with-python > --with-opencl --with-x is built into AC_PATH_XTRA which is a standard autoconf macro. The others originate with a LOC_ARG_WITH macro (which is a shallow wrapper around AC_ARG_WITH). This sets the variable with_foo to "yes" if --with-foo is used with no argument, to "no" if --without-foo is used, to the argument if --with-foo is used with an argument, and to the default value (the third argument of LOC_ARG_WITH, defaulting to "no") if --without-foo isn't used. > Thanks. I’m trying to find out if any of these are hardwired to > specifically look in /usr/.. for stuff. Not by configure.in. AC_PATH_XTRA may have some hardwired defaults, some of the other tests use pkgconf by default. -- Glynn Clements___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] where is GRASS looking for these dependencies?
Thanks. I’m trying to find out if any of these are hardwired to specifically look in /usr/.. for stuff. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Head, Graduate Faculty in Complex Adaptive Systems Science Arizona State University voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu > On Jul 15, 2016, at 1:31 PM, Markus Netelerwrote: > > On Fri, Jul 15, 2016 at 9:27 PM, Michael Barton > wrote: >> Can someone familiar with the GRASS build system tell me where it is looking >> for the following items in the configure string when compiling? >> >> --with-x >> --with-cxx >> --with-opengl=aqua >> --with-python >> --with-opencl > > The --with-x is AFAIK not used in G7.x (not sure if this applies to > Mac OSX, too). > > For the others, as a start, see: > > grep opengl aclocal.m4 configure.in > configure.in:LOC_ARG_WITH(opengl, OpenGL) > configure.in:LOC_ARG_WITH_INC(opengl, OpenGL) > configure.in:LOC_ARG_WITH_LIB(opengl, OpenGL) > configure.in:LOC_ARG_WITH_FRAMEWORK(opengl, OpenGL) > configure.in:AC_MSG_RESULT("$with_opengl") > configure.in:case "$with_opengl" in > configure.in:AC_MSG_ERROR([*** Valid arguments for > --with-opengl= are yes,no,x11,aqua,windows.]) > configure.in:LOC_CHECK_INC_PATH(opengl,OpenGL,OPENGLINC) > configure.in:LOC_CHECK_LIB_PATH(opengl,OpenGL,OPENGL_LIB_PATH) > configure.in:LOC_CHECK_FRAMEWORK_PATH(opengl,OpenGL,OPENGLPATH) > configure.in:LOC_CHECK_INC_PATH(opengl,OpenGL,OPENGLINC) > configure.in:LOC_CHECK_LIB_PATH(opengl,OpenGL,OPENGL_LIB_PATH) > configure.in:LOC_CHECK_LINK(opengl32,[#include > ],[glEnd();],OpenGL,$OPENGL_LIB_PATH,OPENGLLIB) > > grep cxx aclocal.m4 configure.in > configure.in:LOC_ARG_WITH(cxx, C++) > configure.in:PDAL_CPPFLAGS=`"$PDAL_CONFIG" --cxxflags` > configure.in:LOC_CHECK_USE(cxx,C++,USE_CXX) > > etc.. > > Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] where is GRASS looking for these dependencies?
On Fri, Jul 15, 2016 at 9:27 PM, Michael Bartonwrote: > Can someone familiar with the GRASS build system tell me where it is looking > for the following items in the configure string when compiling? > > --with-x > --with-cxx > --with-opengl=aqua > --with-python > --with-opencl The --with-x is AFAIK not used in G7.x (not sure if this applies to Mac OSX, too). For the others, as a start, see: grep opengl aclocal.m4 configure.in configure.in:LOC_ARG_WITH(opengl, OpenGL) configure.in:LOC_ARG_WITH_INC(opengl, OpenGL) configure.in:LOC_ARG_WITH_LIB(opengl, OpenGL) configure.in:LOC_ARG_WITH_FRAMEWORK(opengl, OpenGL) configure.in:AC_MSG_RESULT("$with_opengl") configure.in:case "$with_opengl" in configure.in:AC_MSG_ERROR([*** Valid arguments for --with-opengl= are yes,no,x11,aqua,windows.]) configure.in:LOC_CHECK_INC_PATH(opengl,OpenGL,OPENGLINC) configure.in:LOC_CHECK_LIB_PATH(opengl,OpenGL,OPENGL_LIB_PATH) configure.in:LOC_CHECK_FRAMEWORK_PATH(opengl,OpenGL,OPENGLPATH) configure.in:LOC_CHECK_INC_PATH(opengl,OpenGL,OPENGLINC) configure.in:LOC_CHECK_LIB_PATH(opengl,OpenGL,OPENGL_LIB_PATH) configure.in:LOC_CHECK_LINK(opengl32,[#include ],[glEnd();],OpenGL,$OPENGL_LIB_PATH,OPENGLLIB) grep cxx aclocal.m4 configure.in configure.in:LOC_ARG_WITH(cxx, C++) configure.in:PDAL_CPPFLAGS=`"$PDAL_CONFIG" --cxxflags` configure.in:LOC_CHECK_USE(cxx,C++,USE_CXX) etc.. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] where is GRASS looking for these dependencies?
Can someone familiar with the GRASS build system tell me where it is looking for the following items in the configure string when compiling? --with-x --with-cxx --with-opengl=aqua --with-python --with-opencl Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Head, Graduate Faculty in Complex Adaptive Systems Science Arizona State University voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev