[GRASS-dev] wingrass-addons: manifests
hamish_b at yahoo.com
Mon Dec 5 08:10:59 EST 2011
> when building addons for winGRASS I am having problem with
> creating manifests, see .
> make OBJ.i686-pc-mingw32/i.points.auto.manifest.res
> Any idea what is missing in the compilation script?
do you get the same with another module? It builds for me ok
on linux, but maybe there is some unknown in the newish code..?
I recently fixed the Makefile for that in grass6 addons*, but
until this post I had not noticed MMz had ported it to grass7,
or considered anyone would even attempt that due to the past
i.points interactive Xmon dependency.. (nice!)
[*] some other minor stuff too which might be sync'd, if needed.
?? <addons version="7.0.svn"> in the grass6.xml file?
?? d.barb: why no <description> loaded?
* wxGUI extension removal:
I don't think it is very wise to rely on a volatile generated file on
a remote server to decide which files to delete on my local machine.
Frankly it seems a bit dangerous to me to have a remote script making
those decisions on my behalf. The filenames of what to remove are
entirely predictable (even html/module_*.png), and may well change
between the time of install and the time of removal, so I would
suggest to abandon the <binary><file>s. Was there some win32 reason
to do that, or..?
* wingrass uninstall now also removes the addon dir? I guess it is in case
a replacement install has a different GIS_H version, but what if the user
legitimately put some of their self-authored scripts in there? If that
must stay for some reason, there should at least be a "Are you really sure
you want to do this?" dialog, as non-accidentally deleting users' personal
scripts will not be good for business.
More information about the grass-dev