#1008: WinGrass7 - disable LFS ------------------------------+--------------------------------------------- Reporter: hellik | Owner: [email protected] Type: defect | Status: new Priority: normal | Milestone: 7.0.0 Component: Compiling | Version: svn-trunk Resolution: | Keywords: wingrass Platform: MSWindows Vista | Cpu: x86-32 ------------------------------+--------------------------------------------- Comment (by hellik):
Replying to [comment:9 glynn]: > Replying to [comment:8 glynn]: > > > > in v.patch, r.patch r.li.patchdensity,r.li.patchnum, that seems again to be the problem with UAC and reserverd words for safety in the windows world. :o( > > > > That would be my guess. > > > > > that's interesting, because all manifests for all exe-files are built. > > > > Ah, but they're all built in one operation at the very end of the build process. They need to be built before "<cmd> --html-description" is run to generate the HTML documentation. > > I've changed 7.0 (r41457 and r41458) to build manifests at the same time as the executable and (by default) to embed them into the executable. However, I only have XP, so I can't test this; please test 7.0 on Vista or Win7. It should be possible to build external manifests instead with "make MANIFEST=external". I've had time for only a very quick test for compiling 7.0 on WinVista32 (this time only again time for the ./mswindows/osgeo4w/package.sh- approach, so the diglib- and gem issue doesn't matter here at the moment, and also that installing in C:\OSGeo4W\apps\grass doesn't work; for a very basic testing grass7.0 is starting from C:\OSGeo4W\usr\src\grass_trunk\bin.i686-pc-mingw32). embedding the manifests in the executables works quite well, no compiling errors for v.patch, r.patch r.li.patchdensity,r.li.patchnum etc. and no working/executing errors for v.patch, r.patch. given grass64/65 installed in C:\OSGeo4W\apps\grass and with external manifests, i've seen sometimes a r.patch/v.patch-failure because of the reserverd-words-for-safety-in-the-windows-world-issue. so maybe the embedded manifests would be also an option for grass64? I see that with the embedded manifests the v.patch/r.patch-executables are no longer marked with a mswindows-symbol like the executables without any manifests/with external manifests. so maybe the approach embedding the manifest would be better way? Helmut -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1008#comment:10> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
