B
buttim
Tue, Feb 14, 2017 1:08 AM
For completeness I tried a 64 bits build only to hit a wall of errors in
GeometryEvaluator.cc.
I might have screwed up something though: it's 2AM here and I definitely
need some rest!
--
View this message in context: http://forum.openscad.org/Windows-cross-compilation-tp20413p20424.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
For completeness I tried a 64 bits build only to hit a wall of errors in
GeometryEvaluator.cc.
I might have screwed up something though: it's 2AM here and I definitely
need some rest!
--
View this message in context: http://forum.openscad.org/Windows-cross-compilation-tp20413p20424.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
B
buttim
Sat, Feb 18, 2017 12:10 AM
...stuck
--
View this message in context: http://forum.openscad.org/Windows-cross-compilation-tp20413p20469.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
...stuck
--
View this message in context: http://forum.openscad.org/Windows-cross-compilation-tp20413p20469.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
B
buttim
Fri, Mar 3, 2017 10:46 PM
Since there is absolutely no way to cross compile for Windows, at least on my
PC, I turned to compiling for Ubuntu. After a few corrections I managed to
get the editor enhancements back in the current source base.
Is it worth to extract a patch file and post it here or is my experiment
doomed to fall in limbo again (so better have some TV instead)?
--
View this message in context: http://forum.openscad.org/Windows-cross-compilation-tp20413p20716.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
Since there is absolutely no way to cross compile for Windows, at least on my
PC, I turned to compiling for Ubuntu. After a few corrections I managed to
get the editor enhancements back in the current source base.
Is it worth to extract a patch file and post it here or is my experiment
doomed to fall in limbo again (so better have some TV instead)?
--
View this message in context: http://forum.openscad.org/Windows-cross-compilation-tp20413p20716.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
TP
Torsten Paul
Fri, Mar 3, 2017 11:14 PM
On 03/03/2017 11:46 PM, buttim wrote:
Is it worth to extract a patch file and post it here or is
my experiment doomed to fall in limbo again (so better have
some TV instead)?
Could you put your change into a pull-request on github?
That would make it much easier to check it out on the different
platforms.
ciao,
Torsten.
On 03/03/2017 11:46 PM, buttim wrote:
> Is it worth to extract a patch file and post it here or is
> my experiment doomed to fall in limbo again (so better have
> some TV instead)?
>
Could you put your change into a pull-request on github?
That would make it much easier to check it out on the different
platforms.
ciao,
Torsten.
B
buttim
Fri, Mar 3, 2017 11:35 PM
Sure. Since I'm a newbee can you just outline the correct sequence of
actions? Should I create a new branch or something? I'll be glad to document
on the details, I just need a broad idea.
Thanks
--
View this message in context: http://forum.openscad.org/Windows-cross-compilation-tp20413p20718.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
Sure. Since I'm a newbee can you just outline the correct sequence of
actions? Should I create a new branch or something? I'll be glad to document
on the details, I just need a broad idea.
Thanks
--
View this message in context: http://forum.openscad.org/Windows-cross-compilation-tp20413p20718.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
TP
Torsten Paul
Fri, Mar 3, 2017 11:50 PM
On 03/04/2017 12:35 AM, buttim wrote:
Sure. Since I'm a newbee can you just outline the correct sequence
of actions? Should I create a new branch or something? I'll be glad
to document on the details, I just need a broad idea.
The help entry point on github for this would be
https://help.github.com/articles/fork-a-repo/
I think it's basically (using only command line).
-
get github account if you don't have one already
-
(optional, I think) upload ssh-key to github account
-
clone/fork the openscad repository into your account
git clone git@github.com:<your-account>/openscad.git
cd openscad
git checkout editor-enhancements master
patch ...
git status # to see what's new and changed
git add <new / changed files>
git commit # add short description of the change
git push # might output a warning, in that case use the command suggested
- now the branch should show up on your account in your
openscad repo copy and github should show the option
to create a pull request
ciao,
Torsten.
On 03/04/2017 12:35 AM, buttim wrote:
> Sure. Since I'm a newbee can you just outline the correct sequence
> of actions? Should I create a new branch or something? I'll be glad
> to document on the details, I just need a broad idea.
>
The help entry point on github for this would be
https://help.github.com/articles/fork-a-repo/
I think it's basically (using only command line).
- get github account if you don't have one already
- (optional, I think) upload ssh-key to github account
- clone/fork the openscad repository into your account
git clone git@github.com:<your-account>/openscad.git
cd openscad
git checkout editor-enhancements master
patch ...
git status # to see what's new and changed
git add <new / changed files>
git commit # add short description of the change
git push # might output a warning, in that case use the command suggested
- now the branch should show up on your account in your
openscad repo copy and github should show the option
to create a pull request
ciao,
Torsten.
NH
nop head
Sat, Mar 4, 2017 2:47 AM
Since there is absolutely no way to cross compile for Windows, at least on
my PC,
Not sure what you mean by this. Do you mean you can't make a Windows build
on a non-Windows machine, which is what that literally means. Or do you
have a Windows machine and can't build OpenScad for it?
I am building OpenScad on Win7 using the instructions here:
https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Building_on_Microsoft_Windows.
The resulting .exe runs on Windows via the MSYS2 shell but I can't get it
to run directly from Windows. So I am not sure if it is a real Window's
build or not. Is it a Linux build built on Windows using a Linux emulator?
If it builds on Windows using a Linux emulator does that count as a cross
compiling? It is after all a .exe. Totally confused!
On 3 March 2017 at 23:50, Torsten Paul Torsten.Paul@gmx.de wrote:
On 03/04/2017 12:35 AM, buttim wrote:
Sure. Since I'm a newbee can you just outline the correct sequence
of actions? Should I create a new branch or something? I'll be glad
to document on the details, I just need a broad idea.
The help entry point on github for this would be
https://help.github.com/articles/fork-a-repo/
I think it's basically (using only command line).
-
get github account if you don't have one already
-
(optional, I think) upload ssh-key to github account
-
clone/fork the openscad repository into your account
git clone git@github.com:<your-account>/openscad.git
cd openscad
git checkout editor-enhancements master
patch ...
git status # to see what's new and changed
git add <new / changed files>
git commit # add short description of the change
git push # might output a warning, in that case use the command suggested
- now the branch should show up on your account in your
openscad repo copy and github should show the option
to create a pull request
ciao,
Torsten.
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>Since there is absolutely no way to cross compile for Windows, at least on
my PC,
Not sure what you mean by this. Do you mean you can't make a Windows build
on a non-Windows machine, which is what that literally means. Or do you
have a Windows machine and can't build OpenScad for it?
I am building OpenScad on Win7 using the instructions here:
https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Building_on_Microsoft_Windows.
The resulting .exe runs on Windows via the MSYS2 shell but I can't get it
to run directly from Windows. So I am not sure if it is a real Window's
build or not. Is it a Linux build built on Windows using a Linux emulator?
If it builds on Windows using a Linux emulator does that count as a cross
compiling? It is after all a .exe. Totally confused!
On 3 March 2017 at 23:50, Torsten Paul <Torsten.Paul@gmx.de> wrote:
> On 03/04/2017 12:35 AM, buttim wrote:
> > Sure. Since I'm a newbee can you just outline the correct sequence
> > of actions? Should I create a new branch or something? I'll be glad
> > to document on the details, I just need a broad idea.
> >
> The help entry point on github for this would be
> https://help.github.com/articles/fork-a-repo/
>
> I think it's basically (using only command line).
>
> - get github account if you don't have one already
>
> - (optional, I think) upload ssh-key to github account
>
> - clone/fork the openscad repository into your account
>
> git clone git@github.com:<your-account>/openscad.git
>
> cd openscad
>
> git checkout editor-enhancements master
>
> patch ...
>
> git status # to see what's new and changed
>
> git add <new / changed files>
>
> git commit # add short description of the change
>
> git push # might output a warning, in that case use the command suggested
>
> - now the branch should show up on your account in your
> openscad repo copy and github should show the option
> to create a pull request
>
> ciao,
> Torsten.
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
MK
Marius Kintel
Sat, Mar 4, 2017 4:37 AM
This was related to https://github.com/openscad/openscad/issues/1964
The official Windows build of OpenSCAD is currently built on a Linux server using MXE (http://mxe.cc/), which is capable of cross-compiling Windows binaries from a non-Windows environment. The reason for this is is mostly that we don’t have any core developers who use Windows as their primary platform so we’re lacking some of the expertise needed to maintain a stable native build. MXE has proven to be work pretty well as all the build systems for all dependencies are maintained somewhere else.
-Marius
> On Mar 3, 2017, at 21:47, nop head <nop.head@gmail.com> wrote:
> […] Totally confused!
>
This was related to https://github.com/openscad/openscad/issues/1964
The official Windows build of OpenSCAD is currently built on a Linux server using MXE (http://mxe.cc/), which is capable of cross-compiling Windows binaries from a non-Windows environment. The reason for this is is mostly that we don’t have any core developers who use Windows as their primary platform so we’re lacking some of the expertise needed to maintain a stable native build. MXE has proven to be work pretty well as all the build systems for all dependencies are maintained somewhere else.
-Marius
NH
nop head
Sat, Mar 4, 2017 11:42 AM
The MSYS2 build I am using seems to think it is cross compiling on Linux
but it actually running in Cygwin. So does that class as cross compiling
or is it a native build?
The resulting .exe needs some dlls, so it is not statically linked like the
official Windows build.
On 4 March 2017 at 04:37, Marius Kintel marius@kintel.net wrote:
The MSYS2 build I am using seems to think it is cross compiling on Linux
but it actually running in Cygwin. So does that class as cross compiling
or is it a native build?
The resulting .exe needs some dlls, so it is not statically linked like the
official Windows build.
On 4 March 2017 at 04:37, Marius Kintel <marius@kintel.net> wrote:
>
> > On Mar 3, 2017, at 21:47, nop head <nop.head@gmail.com> wrote:
> > […] Totally confused!
> >
> This was related to https://github.com/openscad/openscad/issues/1964
>
> The official Windows build of OpenSCAD is currently built on a Linux
> server using MXE (http://mxe.cc/), which is capable of cross-compiling
> Windows binaries from a non-Windows environment. The reason for this is is
> mostly that we don’t have any core developers who use Windows as their
> primary platform so we’re lacking some of the expertise needed to maintain
> a stable native build. MXE has proven to be work pretty well as all the
> build systems for all dependencies are maintained somewhere else.
>
> -Marius
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
MK
Marius Kintel
Sat, Mar 4, 2017 5:28 PM
On Mar 4, 2017, at 06:42, nop head nop.head@gmail.com wrote:
The MSYS2 build I am using seems to think it is cross compiling on Linux but it actually running in Cygwin. So does that class as cross compiling or is it a native build?
The MSYS2 build just uses mingw, so it’s not cross compiling.
Perhaps some of the “think it is cross compiling” is actually testing for gcc/glibc/posix vs. Microsoft’s compilers/libraries. Lots of opportunities for cleanup there : /
-Marius
> On Mar 4, 2017, at 06:42, nop head <nop.head@gmail.com> wrote:
>
> The MSYS2 build I am using seems to think it is cross compiling on Linux but it actually running in Cygwin. So does that class as cross compiling or is it a native build?
>
The MSYS2 build just uses mingw, so it’s not cross compiling.
Perhaps some of the “think it is cross compiling” is actually testing for gcc/glibc/posix vs. Microsoft’s compilers/libraries. Lots of opportunities for cleanup there : /
-Marius
