Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
On Sun, Nov 18, 2012 at 1:25 PM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/5 Yves yves.per...@modusfx.com Hi Ruben, All the while I tried all packages, since I`m still oscillating between 32 bit and 64 bit, TDM seemed to be the way to go, at least to compile to compile on Windows for Windows. As far as I can tell, none of the packages you suggested allow cross compiling. With this in mind, which package should I use to compile on Windows for Linux? Virtualbox+your favorite distro You mean if Yves wants a Linux emulator executing on Windows. I understand Yves to want a compiler on Windows targeting Linux. What Yves would need to do is to create a cross compiler to do that. You probably see it coming… which package should I use to compile on Windows for MacOSX? Impossible. No, not impossible. You will need to create a cross compiler targeting MacOSX. In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? No. You may need to build it yourself using the GCC sources. I need to create a document for doing this so I can just point to it. Ruben PS: Your font is huge. The huge font can be mitigated by converting to text mode. -- Earnie -- https://sites.google.com/site/earnieboyd -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
On Mon, Nov 19, 2012 at 1:32 PM, Earnie Boyd ear...@users.sourceforge.net wrote: On Sun, Nov 18, 2012 at 1:25 PM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/5 Yves yves.per...@modusfx.com Hi Ruben, All the while I tried all packages, since I`m still oscillating between 32 bit and 64 bit, TDM seemed to be the way to go, at least to compile to compile on Windows for Windows. As far as I can tell, none of the packages you suggested allow cross compiling. With this in mind, which package should I use to compile on Windows for Linux? Virtualbox+your favorite distro You mean if Yves wants a Linux emulator executing on Windows. I understand Yves to want a compiler on Windows targeting Linux. What Yves would need to do is to create a cross compiler to do that. You probably see it coming… which package should I use to compile on Windows for MacOSX? Impossible. No, not impossible. You will need to create a cross compiler targeting MacOSX. Or use mine. It's a *lot* of work, ./configure make make install won't cut it. In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? No. You may need to build it yourself using the GCC sources. I need to create a document for doing this so I can just point to it. Even better, you could encode your knowledge into patches and fixes for crosstool-ng? Ruben PS: Your font is huge. The huge font can be mitigated by converting to text mode. -- Earnie -- https://sites.google.com/site/earnieboyd -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
On Mon, Nov 19, 2012 at 8:37 AM, Ray Donnelly wrote: On Mon, Nov 19, 2012 at 1:32 PM, Earnie Boyd You may need to build it yourself using the GCC sources. I need to create a document for doing this so I can just point to it. Even better, you could encode your knowledge into patches and fixes for crosstool-ng? Until I write down what it is I think I know then it is only an obscure abstract that lives only with me. And being able to point someone to a here's what's needed document specific to the Windows environment then it remains a mystery to those wanting to learn. I didn't know about crosstool-NG until your post, what does the NG part stand for; it isn't obvious from the page on the net? -- Earnie -- https://sites.google.com/site/earnieboyd -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
ng=next generation in this case. I mention it because they've recently added minGW-w64 as a target, and are looking for new people to help out. I'm hoping to add my darwin cross compilers to it and after that look at running it on MSYS. On Mon, Nov 19, 2012 at 5:05 PM, Earnie Boyd ear...@users.sourceforge.net wrote: On Mon, Nov 19, 2012 at 8:37 AM, Ray Donnelly wrote: On Mon, Nov 19, 2012 at 1:32 PM, Earnie Boyd You may need to build it yourself using the GCC sources. I need to create a document for doing this so I can just point to it. Even better, you could encode your knowledge into patches and fixes for crosstool-ng? Until I write down what it is I think I know then it is only an obscure abstract that lives only with me. And being able to point someone to a here's what's needed document specific to the Windows environment then it remains a mystery to those wanting to learn. I didn't know about crosstool-NG until your post, what does the NG part stand for; it isn't obvious from the page on the net? -- Earnie -- https://sites.google.com/site/earnieboyd -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
2012/11/5 Yves yves.per...@modusfx.com Hi Ruben, All the while I tried all packages, since I`m still oscillating between 32 bit and 64 bit, TDM seemed to be the way to go, at least to compile to compile on Windows for Windows. As far as I can tell, none of the packages you suggested allow cross compiling. With this in mind, which package should I use to compile on Windows for Linux? Virtualbox+your favorite distro You probably see it coming… which package should I use to compile on Windows for MacOSX? Impossible. In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? No. Ruben PS: Your font is huge. Sent from my iPhone On Nov 2, 2012, at 18:11, Yves yves.per...@modusfx.com wrote: Very well, I'll chew on this over the weekend. Your wisdom is appreciated indeed. Thank you very much Ruben. Sent from my iPhone On Nov 2, 2012, at 15:55, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/2 Yves Perron yves.per...@modusfx.com Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Hi Yves, Before I go any further, I'd like to know: - Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** There are several you can choose from: - my Personal buildshttp://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/: I provide native and cross compilers which are nicely up to date. Choose the 4.7.2 package if you want to have the latest stable stuff. - mingwbuilds http://sourceforge.net/projects/mingwbuilds/: another person who reads this list and builds compilers. He often has very specialized features enabled which I reserve for my experimental builds. - TDM GCC http://tdm-gcc.tdragon.net/: a MinGW classic, providing a 32-bit Windows to 64-bit Windows multilib compiler (which can compile for both 32 and 64-bit) All of these are either install+ add mingw*/bin to PATH or run the included envsetup script which does that for you (like with mine). It goes without saying I recommend my toolchain builds ;-) - What would be the best compiler to use to get my code compliant for the other platforms? You should use as much compilers as possible, which in this case means: Visual Studio (which will be the limiting factor in any case), GCC (see above) and Clang (see http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/clang-3.1-release/for more details, read carefully). Clang may not be usable for what you are doing, as it misses certain features required for normal Windows code (like dllexporting classes). It works fine in cases not using that though, but only for 32-bit Windows. To force GCC's strict mode, which is very useful, use the following compiler flags when building: -Wextra -pedantic -std=c++11 Some optional extra flags are: -Wconversion -Wuninitialized -Winit-self -Wmissing-include-dirs -Wstrict-aliasing These options will not ensure your code will work on different OSes, but it will make sure it is standards conformant as much as possible. Note that MinGW inherently uses msvcrt, which means certain C functions may not behave like you would expect. See MSDN in Visual C++ 2003 mode to see the documentation for the functions MinGW exposes. If you're using fancy C++11 library features (which include but are not limited to thread, std::to_string, and regex) you will find GCC's libstdc++ unfortunately lacking. Everything else is usually implemented better than on MSVC though, including tuple. To use CMake, just be sure g++ is in PATH, and run cmake path/to/source -GMinGW Makefiles Hope this helps, Ruben ** I say binary hoping I could avoid compiling compilers because this idea upsets me some how. Thank you very much for reading this. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
Yves, there are a number of compilers on the market for windows which can target mac, linux, windows and embarcadero is one of them. impossible is the wrong word I think. it might be very difficult, but I can't see impossible. the code base might have to change drastically though since the CRT and libraries would be all different at least, only the host would stay the same (making it practically a different GNU compiler almost). I hope I am not wrong. it would be a cross compiler if I am not mistaken, and having something like that would be wonderful (but a lot of work to maintain and make). cross compilers have existed for decades. I think vityan made a nice windows-hosted cross compiler targeting ubuntu and freebsd. it was removed probably because of age. apple has their XCode for apple developers, and I don't know what the license agreement is for that, but I think they have a gcc included in that strangely enough. maybe this is why it's impossible? it's a click license or something probably. From: Ruben Van Boxem vanboxem.ru...@gmail.com To: mingw-w64-public@lists.sourceforge.net Sent: Sunday, November 18, 2012 10:25 AM Subject: Re: [Mingw-w64-public] MinWG64 on Windows, for Windows? 2012/11/5 Yves yves.per...@modusfx.com Hi Ruben, All the while I tried all packages, since I`m still oscillating between 32 bit and 64 bit, TDM seemed to be the way to go, at least to compile to compile on Windows for Windows. As far as I can tell, none of the packages you suggested allow cross compiling. With this in mind, which package should I use to compile on Windows for Linux? Virtualbox+your favorite distro You probably see it coming… which package should I use to compile on Windows for MacOSX? Impossible. In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? No. Ruben PS: Your font is huge. Sent from my iPhone On Nov 2, 2012, at 18:11, Yves yves.per...@modusfx.com wrote: Very well, I'll chew on this over the weekend. Your wisdom is appreciated indeed. Thank you very much Ruben. Sent from my iPhone On Nov 2, 2012, at 15:55, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/2 Yves Perron yves.per...@modusfx.com Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Hi Yves, Before I go any further, I'd like to know: * Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** There are several you can choose from: - my Personal builds: I provide native and cross compilers which are nicely up to date. Choose the 4.7.2 package if you want to have the latest stable stuff. - mingwbuilds: another person who reads this list and builds compilers. He often has very specialized features enabled which I reserve for my experimental builds. - TDM GCC: a MinGW classic, providing a 32-bit Windows to 64-bit Windows multilib compiler (which can compile for both 32 and 64-bit) All of these are either install+ add mingw*/bin to PATH or run the included envsetup script which does that for you (like with mine). It goes without saying I recommend my toolchain builds ;-) * What would be the best compiler to use to get my code compliant for the other platforms? You should use as much compilers as possible, which in this case means: Visual Studio (which will be the limiting factor in any case), GCC (see above) and Clang (see http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/clang-3.1-release/ for more details, read carefully). Clang may not be usable for what you are doing, as it misses certain features required for normal Windows code (like dllexporting classes). It works fine in cases not using that though, but only for 32-bit Windows. To force GCC's strict mode, which is very useful, use the following compiler flags when building: -Wextra -pedantic -std=c++11 Some optional extra flags are: -Wconversion -Wuninitialized -Winit-self -Wmissing-include-dirs -Wstrict-aliasing These options will not ensure your code will work on different OSes, but it will make sure it is standards conformant as much as possible. Note that MinGW inherently uses msvcrt, which means certain C functions may
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
On Nov 18, 2012 6:25 PM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/5 Yves yves.per...@modusfx.com Hi Ruben, All the while I tried all packages, since I`m still oscillating between 32 bit and 64 bit, TDM seemed to be the way to go, at least to compile to compile on Windows for Windows. As far as I can tell, none of the packages you suggested allow cross compiling. With this in mind, which package should I use to compile on Windows for Linux? Virtualbox+your favorite distro You probably see it coming… which package should I use to compile on Windows for MacOSX? Impossible. https://mingw-and-ndk.googlecode.com/files/multiarch-darwin11-cctools127.2-gcc42-5666.3-llvmgcc42-2336.1-Windows-120614.7z... But you need to get your hands on a MacOSX SDK too. In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? No. Ruben PS: Your font is huge. Sent from my iPhone On Nov 2, 2012, at 18:11, Yves yves.per...@modusfx.com wrote: Very well, I'll chew on this over the weekend. Your wisdom is appreciated indeed. Thank you very much Ruben. Sent from my iPhone On Nov 2, 2012, at 15:55, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/2 Yves Perron yves.per...@modusfx.com Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Hi Yves, Before I go any further, I'd like to know: Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** There are several you can choose from: - my Personal builds: I provide native and cross compilers which are nicely up to date. Choose the 4.7.2 package if you want to have the latest stable stuff. - mingwbuilds: another person who reads this list and builds compilers. He often has very specialized features enabled which I reserve for my experimental builds. - TDM GCC: a MinGW classic, providing a 32-bit Windows to 64-bit Windows multilib compiler (which can compile for both 32 and 64-bit) All of these are either install+ add mingw*/bin to PATH or run the included envsetup script which does that for you (like with mine). It goes without saying I recommend my toolchain builds ;-) What would be the best compiler to use to get my code compliant for the other platforms? You should use as much compilers as possible, which in this case means: Visual Studio (which will be the limiting factor in any case), GCC (see above) and Clang (see http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/clang-3.1-release/for more details, read carefully). Clang may not be usable for what you are doing, as it misses certain features required for normal Windows code (like dllexporting classes). It works fine in cases not using that though, but only for 32-bit Windows. To force GCC's strict mode, which is very useful, use the following compiler flags when building: -Wextra -pedantic -std=c++11 Some optional extra flags are: -Wconversion -Wuninitialized -Winit-self -Wmissing-include-dirs -Wstrict-aliasing These options will not ensure your code will work on different OSes, but it will make sure it is standards conformant as much as possible. Note that MinGW inherently uses msvcrt, which means certain C functions may not behave like you would expect. See MSDN in Visual C++ 2003 mode to see the documentation for the functions MinGW exposes. If you're using fancy C++11 library features (which include but are not limited to thread, std::to_string, and regex) you will find GCC's libstdc++ unfortunately lacking. Everything else is usually implemented better than on MSVC though, including tuple. To use CMake, just be sure g++ is in PATH, and run cmake path/to/source -GMinGW Makefiles Hope this helps, Ruben ** I say binary hoping I could avoid compiling compilers because this idea upsets me some how. Thank you very much for reading this. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
that would be nice... From: Yves yves.per...@modusfx.com To: mingw-w64-public@lists.sourceforge.net mingw-w64-public@lists.sourceforge.net Sent: Monday, November 5, 2012 10:49 AM Subject: Re: [Mingw-w64-public] MinWG64 on Windows, for Windows? Hi Ruben, All the while I tried all packages, since I`m still oscillating between 32 bit and 64 bit, TDM seemed to be the way to go, at least to compile to compile on Windows for Windows. As far as I can tell, none of the packages you suggested allow cross compiling. With this in mind, which package should I use to compile on Windows for Linux? You probably see it coming… which package should I use to compile on Windows for MacOSX? In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? Sent from my iPhone On Nov 2, 2012, at 18:11, Yves yves.per...@modusfx.com wrote: Very well, I'll chew on this over the weekend. Your wisdom is appreciated indeed. Thank you very much Ruben. Sent from my iPhone On Nov 2, 2012, at 15:55, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/2 Yves Perron yves.per...@modusfx.com Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Hi Yves, Before I go any further, I'd like to know: * Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** There are several you can choose from: - my Personal builds: I provide native and cross compilers which are nicely up to date. Choose the 4.7.2 package if you want to have the latest stable stuff. - mingwbuilds: another person who reads this list and builds compilers. He often has very specialized features enabled which I reserve for my experimental builds. - TDM GCC: a MinGW classic, providing a 32-bit Windows to 64-bit Windows multilib compiler (which can compile for both 32 and 64-bit) All of these are either install+ add mingw*/bin to PATH or run the included envsetup script which does that for you (like with mine). It goes without saying I recommend my toolchain builds ;-) * What would be the best compiler to use to get my code compliant for the other platforms? You should use as much compilers as possible, which in this case means: Visual Studio (which will be the limiting factor in any case), GCC (see above) and Clang (see http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/clang-3.1-release/ for more details, read carefully). Clang may not be usable for what you are doing, as it misses certain features required for normal Windows code (like dllexporting classes). It works fine in cases not using that though, but only for 32-bit Windows. To force GCC's strict mode, which is very useful, use the following compiler flags when building: -Wextra -pedantic -std=c++11 Some optional extra flags are: -Wconversion -Wuninitialized -Winit-self -Wmissing-include-dirs -Wstrict-aliasing These options will not ensure your code will work on different OSes, but it will make sure it is standards conformant as much as possible. Note that MinGW inherently uses msvcrt, which means certain C functions may not behave like you would expect. See MSDN in Visual C++ 2003 mode to see the documentation for the functions MinGW exposes. If you're using fancy C++11 library features (which include but are not limited to thread, std::to_string, and regex) you will find GCC's libstdc++ unfortunately lacking. Everything else is usually implemented better than on MSVC though, including tuple. To use CMake, just be sure g++ is in PATH, and run cmake path/to/source -GMinGW Makefiles Hope this helps, Ruben ** I say binary hoping I could avoid compiling compilers because this idea upsets me some how. Thank you very much for reading this. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Mingw-w64-public mailing list Mingw-w64
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
With this in mind, which package should I use to compile on Windows for Linux? You probably see it coming… which package should I use to compile on Windows for MacOSX? In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? have a look at crosstool-ng http://crosstool-ng.org/. coupled with Cygwin http://cygwin.com/ on Windows, it should allow all kinds of cross-compilation. just make sure you're patient enough while Cygwin builds the cross-compilers; might take a few hours... ;) Zouzou -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
On Tue, Nov 6, 2012 at 6:50 AM, Zouzou wrote: With this in mind, which package should I use to compile on Windows for Linux? You probably see it coming… which package should I use to compile on Windows for MacOSX? In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? have a look at crosstool-ng http://crosstool-ng.org/. coupled with Cygwin http://cygwin.com/ on Windows, it should allow all kinds of cross-compilation. just make sure you're patient enough while Cygwin builds the cross-compilers; might take a few hours... ;) Or if you want a bit faster cross compiler system use MSYS and mingw-w64 distributed binaries. There is no need to encumber the extra time the Cygwin runtime would add to the process. -- Earnie -- https://sites.google.com/site/earnieboyd -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
Hi Ruben, All the while I tried all packages, since I`m still oscillating between 32 bit and 64 bit, TDM seemed to be the way to go, at least to compile to compile on Windows for Windows. As far as I can tell, none of the packages you suggested allow cross compiling. With this in mind, which package should I use to compile on Windows for Linux? You probably see it coming… which package should I use to compile on Windows for MacOSX? In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? Sent from my iPhone On Nov 2, 2012, at 18:11, Yves yves.per...@modusfx.com wrote: Very well, I'll chew on this over the weekend. Your wisdom is appreciated indeed. Thank you very much Ruben. Sent from my iPhone On Nov 2, 2012, at 15:55, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/2 Yves Perron yves.per...@modusfx.com Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Hi Yves, Before I go any further, I'd like to know: Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** There are several you can choose from: - my Personal builds: I provide native and cross compilers which are nicely up to date. Choose the 4.7.2 package if you want to have the latest stable stuff. - mingwbuilds: another person who reads this list and builds compilers. He often has very specialized features enabled which I reserve for my experimental builds. - TDM GCC: a MinGW classic, providing a 32-bit Windows to 64-bit Windows multilib compiler (which can compile for both 32 and 64-bit) All of these are either install+ add mingw*/bin to PATH or run the included envsetup script which does that for you (like with mine). It goes without saying I recommend my toolchain builds ;-) What would be the best compiler to use to get my code compliant for the other platforms? You should use as much compilers as possible, which in this case means: Visual Studio (which will be the limiting factor in any case), GCC (see above) and Clang (see http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/clang-3.1-release/ for more details, read carefully). Clang may not be usable for what you are doing, as it misses certain features required for normal Windows code (like dllexporting classes). It works fine in cases not using that though, but only for 32-bit Windows. To force GCC's strict mode, which is very useful, use the following compiler flags when building: -Wextra -pedantic -std=c++11 Some optional extra flags are: -Wconversion -Wuninitialized -Winit-self -Wmissing-include-dirs -Wstrict-aliasing These options will not ensure your code will work on different OSes, but it will make sure it is standards conformant as much as possible. Note that MinGW inherently uses msvcrt, which means certain C functions may not behave like you would expect. See MSDN in Visual C++ 2003 mode to see the documentation for the functions MinGW exposes. If you're using fancy C++11 library features (which include but are not limited to thread, std::to_string, and regex) you will find GCC's libstdc++ unfortunately lacking. Everything else is usually implemented better than on MSVC though, including tuple. To use CMake, just be sure g++ is in PATH, and run cmake path/to/source -GMinGW Makefiles Hope this helps, Ruben ** I say binary hoping I could avoid compiling compilers because this idea upsets me some how. Thank you very much for reading this. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- LogMeIn Central: Instant, anywhere, Remote PC access and management.
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
Hi Ruben, All the while I tried all packages, since I`m still oscillating between 32 bit and 64 bit, TDM seemed to be the way to go, at least to compile to compile on Windows for Windows. As far as I can tell, none of the packages you suggested allow cross compiling. With this in mind, which package should I use to compile on Windows for Linux? You probably see it coming… which package should I use to compile on Windows for MacOSX? In another words, what solution is there to cross compile on Windows, for Windows, Linux and MacOSX? Sent from my iPhone On Nov 2, 2012, at 18:11, Yves yves.per...@modusfx.com wrote: Very well, I'll chew on this over the weekend. Your wisdom is appreciated indeed. Thank you very much Ruben. Sent from my iPhone On Nov 2, 2012, at 15:55, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/2 Yves Perron yves.per...@modusfx.com Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Hi Yves, Before I go any further, I'd like to know: Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** There are several you can choose from: - my Personal builds: I provide native and cross compilers which are nicely up to date. Choose the 4.7.2 package if you want to have the latest stable stuff. - mingwbuilds: another person who reads this list and builds compilers. He often has very specialized features enabled which I reserve for my experimental builds. - TDM GCC: a MinGW classic, providing a 32-bit Windows to 64-bit Windows multilib compiler (which can compile for both 32 and 64-bit) All of these are either install+ add mingw*/bin to PATH or run the included envsetup script which does that for you (like with mine). It goes without saying I recommend my toolchain builds ;-) What would be the best compiler to use to get my code compliant for the other platforms? You should use as much compilers as possible, which in this case means: Visual Studio (which will be the limiting factor in any case), GCC (see above) and Clang (see http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/clang-3.1-release/ for more details, read carefully). Clang may not be usable for what you are doing, as it misses certain features required for normal Windows code (like dllexporting classes). It works fine in cases not using that though, but only for 32-bit Windows. To force GCC's strict mode, which is very useful, use the following compiler flags when building: -Wextra -pedantic -std=c++11 Some optional extra flags are: -Wconversion -Wuninitialized -Winit-self -Wmissing-include-dirs -Wstrict-aliasing These options will not ensure your code will work on different OSes, but it will make sure it is standards conformant as much as possible. Note that MinGW inherently uses msvcrt, which means certain C functions may not behave like you would expect. See MSDN in Visual C++ 2003 mode to see the documentation for the functions MinGW exposes. If you're using fancy C++11 library features (which include but are not limited to thread, std::to_string, and regex) you will find GCC's libstdc++ unfortunately lacking. Everything else is usually implemented better than on MSVC though, including tuple. To use CMake, just be sure g++ is in PATH, and run cmake path/to/source -GMinGW Makefiles Hope this helps, Ruben ** I say binary hoping I could avoid compiling compilers because this idea upsets me some how. Thank you very much for reading this. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- LogMeIn Central: Instant, anywhere, Remote PC access and management.
[Mingw-w64-public] MinWG64 on Windows, for Windows?
Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Before I go any further, I'd like to know: * Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** * What would be the best compiler to use to get my code compliant for the other platforms? ** I say binary hoping I could avoid compiling compilers because this idea upsets me some how. Thank you very much for reading this. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
2012/11/2 Yves Perron yves.per...@modusfx.com Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Hi Yves, Before I go any further, I'd like to know: - Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** There are several you can choose from: - my Personal buildshttp://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/: I provide native and cross compilers which are nicely up to date. Choose the 4.7.2 package if you want to have the latest stable stuff. - mingwbuilds http://sourceforge.net/projects/mingwbuilds/: another person who reads this list and builds compilers. He often has very specialized features enabled which I reserve for my experimental builds. - TDM GCC http://tdm-gcc.tdragon.net/: a MinGW classic, providing a 32-bit Windows to 64-bit Windows multilib compiler (which can compile for both 32 and 64-bit) All of these are either install+ add mingw*/bin to PATH or run the included envsetup script which does that for you (like with mine). It goes without saying I recommend my toolchain builds ;-) - What would be the best compiler to use to get my code compliant for the other platforms? You should use as much compilers as possible, which in this case means: Visual Studio (which will be the limiting factor in any case), GCC (see above) and Clang (see http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/clang-3.1-release/for more details, read carefully). Clang may not be usable for what you are doing, as it misses certain features required for normal Windows code (like dllexporting classes). It works fine in cases not using that though, but only for 32-bit Windows. To force GCC's strict mode, which is very useful, use the following compiler flags when building: -Wextra -pedantic -std=c++11 Some optional extra flags are: -Wconversion -Wuninitialized -Winit-self -Wmissing-include-dirs -Wstrict-aliasing These options will not ensure your code will work on different OSes, but it will make sure it is standards conformant as much as possible. Note that MinGW inherently uses msvcrt, which means certain C functions may not behave like you would expect. See MSDN in Visual C++ 2003 mode to see the documentation for the functions MinGW exposes. If you're using fancy C++11 library features (which include but are not limited to thread, std::to_string, and regex) you will find GCC's libstdc++ unfortunately lacking. Everything else is usually implemented better than on MSVC though, including tuple. To use CMake, just be sure g++ is in PATH, and run cmake path/to/source -GMinGW Makefiles Hope this helps, Ruben ** I say binary hoping I could avoid compiling compilers because this idea upsets me some how. Thank you very much for reading this. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
Very well, I'll chew on this over the weekend. Your wisdom is appreciated indeed. Thank you very much Ruben. Sent from my iPhone On Nov 2, 2012, at 15:55, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/2 Yves Perron yves.per...@modusfx.com Greetings everyone, Its been a wild ride for me in the cross-platform compilation world. After several weeks pulling my hair, I figured it might be a good thing to ask for help before I go completely bald. To resume, I do have a fairly complex C++ Visual Studio 10 Win64 project that needs to be maintained on windows and port to Linux and MacOSX. For simplicity sake, let's forget I just said that and let's get down to basics. Here is my setup: Windows 7 CMake 2.8.9 Intel Processor 64 bit I already have my CMake setup running using the Visual Studio 10 Win64 compiler and it works beautifully. Now, to get things rolling, I'd like to compile the same project with MinWG64 on Windows, for Windows. Hi Yves, Before I go any further, I'd like to know: Which MinGW64 binary package should I get from http://sourceforge.net/projects/mingw-w64?** There are several you can choose from: - my Personal builds: I provide native and cross compilers which are nicely up to date. Choose the 4.7.2 package if you want to have the latest stable stuff. - mingwbuilds: another person who reads this list and builds compilers. He often has very specialized features enabled which I reserve for my experimental builds. - TDM GCC: a MinGW classic, providing a 32-bit Windows to 64-bit Windows multilib compiler (which can compile for both 32 and 64-bit) All of these are either install+ add mingw*/bin to PATH or run the included envsetup script which does that for you (like with mine). It goes without saying I recommend my toolchain builds ;-) What would be the best compiler to use to get my code compliant for the other platforms? You should use as much compilers as possible, which in this case means: Visual Studio (which will be the limiting factor in any case), GCC (see above) and Clang (see http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/clang-3.1-release/ for more details, read carefully). Clang may not be usable for what you are doing, as it misses certain features required for normal Windows code (like dllexporting classes). It works fine in cases not using that though, but only for 32-bit Windows. To force GCC's strict mode, which is very useful, use the following compiler flags when building: -Wextra -pedantic -std=c++11 Some optional extra flags are: -Wconversion -Wuninitialized -Winit-self -Wmissing-include-dirs -Wstrict-aliasing These options will not ensure your code will work on different OSes, but it will make sure it is standards conformant as much as possible. Note that MinGW inherently uses msvcrt, which means certain C functions may not behave like you would expect. See MSDN in Visual C++ 2003 mode to see the documentation for the functions MinGW exposes. If you're using fancy C++11 library features (which include but are not limited to thread, std::to_string, and regex) you will find GCC's libstdc++ unfortunately lacking. Everything else is usually implemented better than on MSVC though, including tuple. To use CMake, just be sure g++ is in PATH, and run cmake path/to/source -GMinGW Makefiles Hope this helps, Ruben ** I say binary hoping I could avoid compiling compilers because this idea upsets me some how. Thank you very much for reading this. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one
