Is anyone able to build on Win 7 (original) (raw)
Fredrik Öhrström fredrik.ohrstrom at oracle.com
Thu Feb 2 13:22:31 UTC 2012
- Previous message (by thread): Is anyone able to build on Win 7
- Next message (by thread): Is anyone able to build on Win 7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2012-02-02 00:10, Kelly O'Hair skrev:
I don't know what the current state is. The CYGWIN community seemed pretty adamant that they wanted to stamp out all drive letter pathnames. As I understood it, it's not so much the version of make.exe, but how the make.exe was built. Some kind of 'allow drive letter paths' option needs to be turned on when building.
I created a neat solution to get around this drive letter problem in the new build-infra/jdk8 (jdk7) forest.
The configure script compiles an executable called uncygdrive.exe
The make variables that point to tools that do not understand /cygdrive paths, like CC:=cl.exe and JAVA:=java.exe are rewritten to:
CC:=uncygdrive.exe cl.exe JAVA:=uncygdrive.exe java.exe
As you can guess, the uncygdrive command parses the command line and rewrites any /cygdrive/c/ into just c:/ (likewise for any other drive letter). It even enters into @files and creates a temporary file with adjusted content. Then it execs the new adjusted command line.
Works great and the Makefiles become much simpler since you can just use /cygdrive everywhere!
A more important problem is the dreaded slowdown of cygwin on 64 bit windows. It is believed to be the fork simulation gone haywaire when dealing with 64 bit address space, but what do I know.....
//Fredrik
- Previous message (by thread): Is anyone able to build on Win 7
- Next message (by thread): Is anyone able to build on Win 7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]