the idea was that wx related docs should
not be generated if GRASS
is compiled without wxwidgets. That's why the
condition was added.
Markus
On 11/30/11, svn_grass@osgeo.org <svn_grass@osgeo.org> wrote:
Author: martinl
Date: 2011-11-30 10:21:36 -0800 (Wed, 30 Nov 2011)
New Revision: 49437
Modified:
grass/trunk/gui/wxpython/Makefile
Log:
don't conditionize `wxpython`, there is nothing to compile
`--with-widgets` is used during compilation, see eg.
`vizualization/wximgview`
the idea was that wx related docs should
not be generated if GRASS
is compiled without wxwidgets. That's why the
condition was added.
hm, the problem is that `--with-wxwidgets` should control only if
modules which uses wxWidgets library are compiled or not. Than we
would probably need a new switch which would optionally disable
installing wxGUI code, eg. `--disable-wxgui`.
On Wed, Nov 30, 2011 at 7:53 PM, Martin Landa <landa.martin@gmail.com> wrote:
2011/11/30 Markus Neteler <neteler@osgeo.org>:
the idea was that wx related docs should
not be generated if GRASS
is compiled without wxwidgets. That's why the
condition was added.
hm, the problem is that `--with-wxwidgets` should control only if
modules which uses wxWidgets library are compiled or not. Than we
would probably need a new switch which would optionally disable
installing wxGUI code, eg. `--disable-wxgui`.
Apparently I don't understand the difference
Compiling with --without-wxwidgets I thought would be the way to
get only a "core GRASS" version without GUI.
hm, the problem is that `--with-wxwidgets` should control only if
modules which uses wxWidgets library are compiled or not. Than we
would probably need a new switch which would optionally disable
installing wxGUI code, eg. `--disable-wxgui`.
Apparently I don't understand the difference
Compiling with --without-wxwidgets I thought would be the way to
get only a "core GRASS" version without GUI.
no, it's not purpose of `--with(out)-widgets` switch. It was
introduced to control compilation of modules which are linked against
wxWidgets library, eg. `wximgview`. In other words, with
`--without-wxwidgets` you should get GRASS without modules which are
using wxWidgets library directly. It's not the case of wxGUI. Probably
we should think about introducing a new configure switch for disabling
wxGUI.
no, it's not purpose of `--with(out)-widgets` switch. It was
introduced to control compilation of modules which are linked against
wxWidgets library, eg. `wximgview`. In other words, with
`--without-wxwidgets` you should get GRASS without modules which are
using wxWidgets library directly. It's not the case of wxGUI. Probably
we should think about introducing a new configure switch for disabling
wxGUI.
similarly `--without-python` doesn't mean that python scripts will be
no installed. It just means that the programs which are built against
python libraries will be not compiled.
building grass 7 with `make -j 8` on a muti-cpu machine ends with a
build error in the wxpython docs dir. `cd gui/wxpython/` and running
`make` has no error, so I suspect it is just a Makefile dependency thing.
building 6.4 and 6.5 completes without error. (58 sec for full compile!)
building grass 7 with `make -j 8` on a muti-cpu machine ends with a
build error in the wxpython docs dir. `cd gui/wxpython/` and running
`make` has no error, so I suspect it is just a Makefile dependency thing.
> building grass 7 with `make -j 8` on a muti-cpu machine ends with a
> build error in the wxpython docs dir. `cd gui/wxpython/` and running
> `make` has no error, so I suspect it is just a Makefile dependency thing.
