#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 glynn):
Replying to [comment:10 hellik]: > 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. > 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? It would probably be the better approach, but I don't know how easy it would be. The build system has been cleaned up a lot in 7.0; there were only a handful of executables which required special treatment, the rest being handled automatically by changes to Compile.make. The 6.x Makefiles have far more special cases. A large part of the problem is that 6.x tries to support older versions of GNU make, while 7.0 requires version 3.81. That might not seem like much of a constraint, given that 3.81 has been out for nearly four years, but both MacOSX and MSys were using 3.79 (nearly ten years old) until fairly recently. If someone wants to try back-porting the changes to 6.x: for normal modules, you would just need to modify the linking rule for $(BIN)/$(PGM)$(EXE) in Module.make. But you'll find dozens of programs with their own linking commands in their Makefiles (grep for LDFLAGS). You can check whether an executable has an embedded manifest by running "objdump -h" on it and looking for a ".rsrc" section. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1008#comment:11> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
