discuss@lists.openscad.org

OpenSCAD general discussion Mailing-list

View all threads

Compile OpenSCAD on Windows?

S
Scalpel78
Thu, Dec 18, 2014 7:12 PM

$ flex --version
flex 2.5.39

--
View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10613.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

$ flex --version flex 2.5.39 -- View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10613.html Sent from the OpenSCAD mailing list archive at Nabble.com.
M
mx
Thu, Dec 18, 2014 8:36 PM

Then I don't know, that one should do fine.


lazy.scad - http://www.thingiverse.com/thing:512443

View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10614.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

Then I don't know, that one should do fine. ----- lazy.scad - http://www.thingiverse.com/thing:512443 -- View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10614.html Sent from the OpenSCAD mailing list archive at Nabble.com.
MK
Marius Kintel
Thu, Dec 18, 2014 9:26 PM

On Dec 18, 2014, at 13:02 PM, Scalpel78 frode@lillerud.no wrote:

Yes, that page is up-to-date with the setup I have used.

Looks like the OpenCSG fixes didn’t make it to that page. It still tries to build examples and link with GLUT.

-Marius

On Dec 18, 2014, at 13:02 PM, Scalpel78 <frode@lillerud.no> wrote: > Yes, that page is up-to-date with the setup I have used. > Looks like the OpenCSG fixes didn’t make it to that page. It still tries to build examples and link with GLUT. -Marius
S
Scalpel78
Fri, Dec 19, 2014 6:25 PM

Right, I forgot to document that part. But I did it manually on my machine,
so I don't think that causes that 'lexer' error.

Is there an easy way to apply the .patch file to avoid having to make each
change manually?

--
View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10643.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

Right, I forgot to document that part. But I did it manually on my machine, so I don't think that causes that 'lexer' error. Is there an easy way to apply the .patch file to avoid having to make each change manually? -- View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10643.html Sent from the OpenSCAD mailing list archive at Nabble.com.
TP
Torsten Paul
Fri, Dec 19, 2014 6:30 PM

On 12/19/2014 07:25 PM, Scalpel78 wrote:

Is there an easy way to apply the .patch file to avoid having to make each
change manually?

Yes, if you have the OpenSCAD sources cloned and made the changes, you can
generate the full diff using "git diff > file.patch".

This could then be applied by "patch -p1 < file.patch" again on clean sources.

ciao,
Torsten.

On 12/19/2014 07:25 PM, Scalpel78 wrote: > Is there an easy way to apply the .patch file to avoid having to make each > change manually? > Yes, if you have the OpenSCAD sources cloned and made the changes, you can generate the full diff using "git diff > file.patch". This could then be applied by "patch -p1 < file.patch" again on clean sources. ciao, Torsten.
S
Scalpel78
Fri, Dec 19, 2014 7:09 PM

I got one step further by running the flex command in msys2 bash:

$ flex -P lexer -o src/lexer.lexer.cpp src/lexer.l

That ran without errors.

Now when I try to build in Qt Creator I get this error:

20:03:01: Starting: "C:\msys64\mingw64\bin\mingw32-make.exe"
C:/msys64/mingw64/bin/mingw32-make -f Makefile.Debug
mingw32-make[1]: Entering directory 'C:/openscad/openscad'
bison -d -p parser -o src/parser_yacc.cpp src/parser.y && if [[ -e
src/parser_yacc.hpp ]] ; then mv src/parser_yacc.hpp src/parser_yacc.h ; fi
0 [main] sh 5524 sync_with_child: child 5184(0x164) died before
initialization with status code 0xC0000142
25 [main] sh 5524 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
Makefile.Debug:568: recipe for target 'src/parser_yacc.cpp' failed
mingw32-make[1]: *** [src/parser_yacc.cpp] Error 128
mingw32-make[1]: Leaving directory 'C:/openscad/openscad'
Makefile:34: recipe for target 'debug' failed
mingw32-make: *** [debug] Error 2
20:03:04: The process "C:\msys64\mingw64\bin\mingw32-make.exe" exited with
code 2.
Error while building/deploying project openscad (kit: Desktop Qt 5.3
MinGW-w64 64bit (MSYS2))
When executing step "Make"
20:03:04: Elapsed time: 00:03.

--
View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10645.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

I got one step further by running the flex command in msys2 bash: $ flex -P lexer -o src/lexer.lexer.cpp src/lexer.l That ran without errors. Now when I try to build in Qt Creator I get this error: 20:03:01: Starting: "C:\msys64\mingw64\bin\mingw32-make.exe" C:/msys64/mingw64/bin/mingw32-make -f Makefile.Debug mingw32-make[1]: Entering directory 'C:/openscad/openscad' bison -d -p parser -o src/parser_yacc.cpp src/parser.y && if [[ -e src/parser_yacc.hpp ]] ; then mv src/parser_yacc.hpp src/parser_yacc.h ; fi 0 [main] sh 5524 sync_with_child: child 5184(0x164) died before initialization with status code 0xC0000142 25 [main] sh 5524 sync_with_child: *** child state waiting for longjmp /usr/bin/sh: fork: Resource temporarily unavailable Makefile.Debug:568: recipe for target 'src/parser_yacc.cpp' failed mingw32-make[1]: *** [src/parser_yacc.cpp] Error 128 mingw32-make[1]: Leaving directory 'C:/openscad/openscad' Makefile:34: recipe for target 'debug' failed mingw32-make: *** [debug] Error 2 20:03:04: The process "C:\msys64\mingw64\bin\mingw32-make.exe" exited with code 2. Error while building/deploying project openscad (kit: Desktop Qt 5.3 MinGW-w64 64bit (MSYS2)) When executing step "Make" 20:03:04: Elapsed time: 00:03. -- View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10645.html Sent from the OpenSCAD mailing list archive at Nabble.com.
S
Scalpel78
Fri, Dec 19, 2014 7:20 PM

I've updated the documentation with the changes from the .patch file.

--
View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10646.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

I've updated the documentation with the changes from the .patch file. -- View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10646.html Sent from the OpenSCAD mailing list archive at Nabble.com.
TP
Torsten Paul
Sat, Dec 20, 2014 6:57 PM

Thanks to the MSYS2 developers, all dependencies needed for OpenSCAD are
available as MSYS2 packages now and can simply be installed using pacman.

I've updated the wiki page...
https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Building_on_Microsoft_Windows

Note that there's still an issue with QScintilla crashing when using debug
build (error: "QWidget: Must construct a QApplication before a QWidget").

Anyone having an idea what's wrong there?

The release build does work.

ciao,
Torsten.

Thanks to the MSYS2 developers, all dependencies needed for OpenSCAD are available as MSYS2 packages now and can simply be installed using pacman. I've updated the wiki page... https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Building_on_Microsoft_Windows Note that there's still an issue with QScintilla crashing when using debug build (error: "QWidget: Must construct a QApplication before a QWidget"). Anyone having an idea what's wrong there? The release build does work. ciao, Torsten.
S
Scalpel78
Sat, Dec 20, 2014 7:20 PM

That is awesome! Thanks, I'll try to reinstall everything using msys2.

--
View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10667.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

That is awesome! Thanks, I'll try to reinstall everything using msys2. -- View this message in context: http://forum.openscad.org/Compile-OpenSCAD-on-Windows-tp10516p10667.html Sent from the OpenSCAD mailing list archive at Nabble.com.
TP
Torsten Paul
Sat, Dec 20, 2014 10:48 PM

Compilation on MSYS2 should now work without any changes in the OpenSCAD sources.

Many thanks to Alexpux from MSYS2 for the help.

We might get a debug version from QScintilla as package too, that would enable
us to create debug builds later.

In the meantime it would require to build debug versions of the QScintilla
library.

ciao,
Torsten.

Compilation on MSYS2 should now work without any changes in the OpenSCAD sources. Many thanks to Alexpux from MSYS2 for the help. We might get a debug version from QScintilla as package too, that would enable us to create debug builds later. In the meantime it would require to build debug versions of the QScintilla library. ciao, Torsten.
loading...