You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built dmake on Windows using mingw and msys. Used a patch similar to the msys patch listed here. I'm trying to work with the FHS standard to determine where files are placed under msys. When I built dmake, it placed the .mk files under usr\local\share\startup which makes sense and follows the FHS standard. When I run dmake, it's looking for the files in startup subdirectory beneath the bin directory where the dmake executable is (usr\local\bin\startup).
There's a line in configure that switches it to look for DMAKEROOT at $datarootdir/share/startup, but it's only set to work for unix like machines:
if test x$OS_TYPE = xunix; then
DMAKEROOT_H_LINE1='"DMAKEROOT := '${dmakerootprefix}'/startup",'
fi
I like the fact that it installs support files in $datarootdir/share/. However, it would be even nicer if it could actually find the files that it installs to that directory. Thanks.
The text was updated successfully, but these errors were encountered:
mohawk2
changed the title
Configuration file not found
Configuration file on mingw/msys put in different place from where looks
Aug 29, 2014
I built dmake on Windows using mingw and msys. Used a patch similar to the msys patch listed here. I'm trying to work with the FHS standard to determine where files are placed under msys. When I built dmake, it placed the .mk files under usr\local\share\startup which makes sense and follows the FHS standard. When I run dmake, it's looking for the files in startup subdirectory beneath the bin directory where the dmake executable is (usr\local\bin\startup).
There's a line in configure that switches it to look for DMAKEROOT at $datarootdir/share/startup, but it's only set to work for unix like machines:
Had to work around the issue with:
I like the fact that it installs support files in $datarootdir/share/. However, it would be even nicer if it could actually find the files that it installs to that directory. Thanks.
The text was updated successfully, but these errors were encountered: