Re: [Mingw-w64-public] ironCrate

2012-12-02 Thread JonY
On 12/2/2012 12:55, Jon wrote: However, if you choose to use autotools, to better support the build-for-windows-on-windows scenario I ask that you also maintain a mingw32-make compatible Makefile. IIRC, this was Ozkan's suggestion near the very beginning of the discussion. Do you mean by

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread deneme.true
This is intriguing. Can you give some detail on how it works for cross compiling? xml file definition regarding libraries and executables exists in *.bkl files(similar to ant), bakefile will generate the makefiles from *.bkl files for specific make tools. It works perfectly in wxWidgets.

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread Earnie Boyd
On Sat, Dec 1, 2012 at 1:47 AM, Vincent Torri wrote: On Sat, Dec 1, 2012 at 6:49 AM, NightStrike wrote: Really, I haven't seen any build system that I think is wonderful. autotools works for us, but it's not great. I've used a lot... even scons. just for curiosity : what do you think of

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread Jon
As for your concerns about CMake being available or not: it's available from all Linux and BSD variants I know because more and more projects are moving to CMake because more and more projects are concerned about cross-platform, including MSVC. It's not something esoteric. As far as

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread JonY
On 12/2/2012 06:27, Jon wrote: As for your concerns about CMake being available or not: it's available from all Linux and BSD variants I know because more and more projects are moving to CMake because more and more projects are concerned about cross-platform, including MSVC. It's not something

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread Jon
As for your concerns about CMake being available or not: it's available from all Linux and BSD variants I know because more and more projects are moving to CMake because more and more projects are concerned about cross-platform, including MSVC. It's not something esoteric. As far as

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread Jon
However, if you choose to use autotools, to better support the build-for-windows-on-windows scenario I ask that you also maintain a mingw32-make compatible Makefile. IIRC, this was Ozkan's suggestion near the very beginning of the discussion. Do you mean by this not msys ? Yes. I

Re: [Mingw-w64-public] ironCrate

2012-11-30 Thread NightStrike
On Mon, Nov 12, 2012 at 3:22 AM, Xiaofan Chen xiaof...@gmail.com wrote: On Mon, Nov 12, 2012 at 3:55 PM, Pau Garcia i Quiles pgqui...@elpauer.org wrote: As for your concerns about CMake being available or not: it's available from all Linux and BSD variants I know because more and more

Re: [Mingw-w64-public] ironCrate

2012-11-30 Thread NightStrike
On Fri, Nov 30, 2012 at 10:13 AM, Zouzou inter...@123gen.com wrote: On 30/11/12 15:29, NightStrike wrote: In the autotools world, there is a very defined and extremely enforced concept that above all, our goal is to make it *TRIVIAL* for the end user to compile your software. Now let's clarify

Re: [Mingw-w64-public] ironCrate

2012-11-30 Thread deneme.true
Hello, As I know, wxWidgets uses bakefile(http://www.bakefile.org/index.html) system. Probably, bakefile is good for cross building of Makefiles for nmake,mingw-make,make etc. -- Keep yourself connected to Go Parallel:

Re: [Mingw-w64-public] ironCrate

2012-11-30 Thread JonY
On 12/1/2012 06:49, Pau Garcia i Quiles wrote: Now of course, we could try to provide these system-specific files that cmake should be giving us for free, but then we'd have to maintain (thus somehow be able to test) every conceivable system that our users might have or want to use. No,

Re: [Mingw-w64-public] ironCrate

2012-11-30 Thread NightStrike
On Fri, Nov 30, 2012 at 12:36 PM, deneme.true deneme.t...@gmail.com wrote: Hello, As I know, wxWidgets uses bakefile(http://www.bakefile.org/index.html) system. Probably, bakefile is good for cross building of Makefiles for nmake,mingw-make,make etc. This is intriguing. Can you give some

Re: [Mingw-w64-public] ironCrate

2012-11-30 Thread NightStrike
On Fri, Nov 30, 2012 at 12:49 PM, Pau Garcia i Quiles pgqui...@elpauer.org wrote: On Fri, Nov 30, 2012 at 3:29 PM, NightStrike nightstr...@gmail.com wrote: [...] In the cmake world, to do the same thing, Dave has to be a lot more knowledgeable of the internals of our project. He needs to

Re: [Mingw-w64-public] ironCrate

2012-11-30 Thread Vincent Torri
On Sat, Dec 1, 2012 at 6:49 AM, NightStrike nightstr...@gmail.com wrote: Really, I haven't seen any build system that I think is wonderful. autotools works for us, but it's not great. I've used a lot... even scons. just for curiosity : what do you think of jam or one of its derivatives

Re: [Mingw-w64-public] ironCrate

2012-11-12 Thread Xiaofan Chen
On Mon, Nov 12, 2012 at 3:55 PM, Pau Garcia i Quiles pgqui...@elpauer.org wrote: As for your concerns about CMake being available or not: it's available from all Linux and BSD variants I know because more and more projects are moving to CMake because more and more projects are concerned about

Re: [Mingw-w64-public] ironCrate

2012-11-12 Thread JonY
On 11/12/2012 16:22, Xiaofan Chen wrote: On Mon, Nov 12, 2012 at 3:55 PM, Pau Garcia i Quiles pgqui...@elpauer.org wrote: As for your concerns about CMake being available or not: it's available from all Linux and BSD variants I know because more and more projects are moving to CMake because

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Sun, Nov 11, 2012 at 2:39 AM, JonY jo...@users.sourceforge.net wrote: It's unfortunate you both had bad experiences with cmake. Cmake really is quite powerful, and recent syntax mods make it friendlier to use. For example, I contributed the following cmake build scripts to the mruby

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread JonY
On 11/11/2012 15:59, Pau Garcia i Quiles wrote: On Sun, Nov 11, 2012 at 2:39 AM, JonY jo...@users.sourceforge.net wrote: It's unfortunate you both had bad experiences with cmake. Cmake really is quite powerful, and recent syntax mods make it friendlier to use. For example, I contributed

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Ruben Van Boxem
Op 11 nov. 2012 09:27 schreef JonY jo...@users.sourceforge.net het volgende: On 11/11/2012 15:59, Pau Garcia i Quiles wrote: On Sun, Nov 11, 2012 at 2:39 AM, JonY jo...@users.sourceforge.net wrote: It's unfortunate you both had bad experiences with cmake. Cmake really is quite powerful,

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread niXman
If I only could, I on a global scale would forbid autotools use, and I would provide criminal punishment for violation of this prohibition =) -- Regards, niXman ___ Dual-target(32 64-bit) MinGW compilers for 32 and 64-bit Windows:

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Sun, Nov 11, 2012 at 9:43 AM, niXman i.nix...@gmail.com wrote: If I only could, I on a global scale would forbid autotools use, and I would provide criminal punishment for violation of this prohibition =) IMHO, autotools are perfectly fine if you are on a Unix-based operating system. The

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Sun, Nov 11, 2012 at 9:26 AM, JonY jo...@users.sourceforge.net wrote: Sounds like they are reinventing autotools. As Ruben says, it's not the case. The main problem with autotools is they do not support Windows. Even with CoApp, autotools support is far from *acceptable* on Windows. A

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread JonY
On 11/11/2012 16:34, Ruben Van Boxem wrote: I think he means macro and module files. Usually you distribute Sounds like they are reinventing autotools. Lol, no. See the https://github.com/mruby/mruby/blob/master/cmake/modules/IntrospectSystem.cmake example. Wrong. Instead of

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Sun, Nov 11, 2012 at 10:14 AM, JonY jo...@users.sourceforge.net wrote: On 11/11/2012 16:42, Pau Garcia i Quiles wrote: On Sun, Nov 11, 2012 at 9:26 AM, JonY jo...@users.sourceforge.net wrote: Sounds like they are reinventing autotools. As Ruben says, it's not the case. The main problem

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Sun, Nov 11, 2012 at 10:05 AM, JonY jo...@users.sourceforge.net wrote: Sounds like they are reinventing autotools. Lol, no. See the https://github.com/mruby/mruby/blob/master/cmake/modules/IntrospectSystem.cmake example. How is this different from what you would to in configure.ac in

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread JonY
On 11/11/2012 18:02, Pau Garcia i Quiles wrote: Any decent build system needs that kind of constructs. Is the CMake syntax a bit different from autotools'? Sure. So what? With CMake you do exactly the same checks you did with autotools, only you may need to consider some Windows specifics

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread niXman
2012/11/11 Kai Tietz: So any help for it is most welcome. The build-system is an important issue, but even more we need developers/reviewers of it and a lot of support :) I wish to take part in development/testing of this project. Where I can get the sources? -- Regards, niXman

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Kai Tietz
2012/11/11 niXman i.nix...@gmail.com: 2012/11/11 Kai Tietz: So any help for it is most welcome. The build-system is an important issue, but even more we need developers/reviewers of it and a lot of support :) I wish to take part in development/testing of this project. Where I can get the

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Sun, Nov 11, 2012 at 11:27 AM, JonY jo...@users.sourceforge.net wrote: What were the rigidities? Maybe I can help We need to a way to inject .a libraries with additional objects compiled from a different step, See add_library(OBJECT):

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Sun, Nov 11, 2012 at 11:38 AM, Kai Tietz ktiet...@googlemail.com wrote: The ironCrate project has as one goal that it shall be API-compatible to msvcr*.dll (means best providing same API as msvcr100.dll from user-perspective. For sure I won't be able - and don't intent to make it 100%

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Ruben Van Boxem
2012/11/11 Kai Tietz ktiet...@googlemail.com 2012/11/11 niXman i.nix...@gmail.com: 2012/11/11 Kai Tietz: So any help for it is most welcome. The build-system is an important issue, but even more we need developers/reviewers of it and a lot of support :) I wish to take part in

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread JonY
On 11/11/2012 18:50, Pau Garcia i Quiles wrote: On Sun, Nov 11, 2012 at 11:27 AM, JonY jo...@users.sourceforge.net wrote: What were the rigidities? Maybe I can help We need to a way to inject .a libraries with additional objects compiled from a different step, See add_library(OBJECT):

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Jon
On Sun, 11 Nov 2012 19:13:04 +0800 JonY jo...@users.sourceforge.net wrote: On 11/11/2012 18:50, Pau Garcia i Quiles wrote: On Sun, Nov 11, 2012 at 11:27 AM, JonY jo...@users.sourceforge.net wrote: What were the rigidities? Maybe I can help We need to a way to inject .a libraries with

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Sun, Nov 11, 2012 at 7:05 PM, Jon jon.for...@gmail.com wrote: So here's the question. Can the method I use when cross-compiling, namely, use cmake's `ExternalProject` module (causes cmake to run itself and generate artifacts in a different dir) to pre-build an environment on the build

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread JonY
On 11/12/2012 03:36, Pau Garcia i Quiles wrote: On Sun, Nov 11, 2012 at 7:05 PM, Jon wrote: So here's the question. Can the method I use when cross-compiling, namely, use cmake's `ExternalProject` module (causes cmake to run itself and generate artifacts in a different dir) to pre-build

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Jon
On Mon, 12 Nov 2012 07:14:42 +0800 JonY jo...@users.sourceforge.net wrote: On 11/12/2012 03:36, Pau Garcia i Quiles wrote: On Sun, Nov 11, 2012 at 7:05 PM, Jon wrote: So here's the question. Can the method I use when cross-compiling, namely, use cmake's `ExternalProject` module

Re: [Mingw-w64-public] ironCrate

2012-11-11 Thread Pau Garcia i Quiles
On Mon, Nov 12, 2012 at 12:14 AM, JonY jo...@users.sourceforge.net wrote: From what I gather, I'll need to: 1. Write an external tool/driver to do this. 2. Split into subprojects. 3. Have cmake call itself recursively. Errr... no 1. Write a CMakeLists.txt for the compiled-to-host-platform

[Mingw-w64-public] ironCrate

2012-11-10 Thread Ruben Van Boxem
Hi, I have the crazy idea to help with ironCrate. I have written a small CMakeLists.txt file to get automated compilation working (I know you guys favor autotools, I don't). I am running into some issues building the source from the get-go. I wanted to ask if I could just start trying to fix

Re: [Mingw-w64-public] ironCrate

2012-11-10 Thread Luis Lavena
On Sat, Nov 10, 2012 at 10:54 AM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: Hi, I have the crazy idea to help with ironCrate. I have written a small CMakeLists.txt file to get automated compilation working (I know you guys favor autotools, I don't). I am running into some issues

Re: [Mingw-w64-public] ironCrate

2012-11-10 Thread Ozkan Sezer
On 11/10/12, Luis Lavena luislav...@gmail.com wrote: On Sat, Nov 10, 2012 at 10:54 AM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: Hi, I have the crazy idea to help with ironCrate. I have written a small CMakeLists.txt file to get automated compilation working (I know you guys favor

Re: [Mingw-w64-public] ironCrate

2012-11-10 Thread Ruben Van Boxem
2012/11/10 Ozkan Sezer seze...@gmail.com On 11/10/12, Luis Lavena luislav...@gmail.com wrote: On Sat, Nov 10, 2012 at 10:54 AM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: Hi, I have the crazy idea to help with ironCrate. I have written a small CMakeLists.txt file to get

Re: [Mingw-w64-public] ironCrate

2012-11-10 Thread Ozkan Sezer
On 11/10/12, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/10 Ozkan Sezer seze...@gmail.com On 11/10/12, Luis Lavena luislav...@gmail.com wrote: On Sat, Nov 10, 2012 at 10:54 AM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: Hi, I have the crazy idea to help with

Re: [Mingw-w64-public] ironCrate

2012-11-10 Thread JonY
On 11/10/2012 23:39, Ozkan Sezer wrote: On 11/10/12, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/10 Ozkan Sezer seze...@gmail.com On 11/10/12, Luis Lavena luislav...@gmail.com wrote: On Sat, Nov 10, 2012 at 10:54 AM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: Hi, I have

Re: [Mingw-w64-public] ironCrate

2012-11-10 Thread Jon
On Sun, 11 Nov 2012 01:22:18 +0800 JonY jo...@users.sourceforge.net wrote: On 11/10/2012 23:39, Ozkan Sezer wrote: On 11/10/12, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2012/11/10 Ozkan Sezer seze...@gmail.com On 11/10/12, Luis Lavena luislav...@gmail.com wrote: On Sat, Nov 10,

Re: [Mingw-w64-public] ironCrate

2012-11-10 Thread JonY
On 11/11/2012 02:22, Jon wrote: It's unfortunate you both had bad experiences with cmake. Cmake really is quite powerful, and recent syntax mods make it friendlier to use. For example, I contributed the following cmake build scripts to the mruby project

Re: [Mingw-w64-public] ironCrate

2012-11-10 Thread Jon
On Sun, 11 Nov 2012 09:39:26 +0800 JonY jo...@users.sourceforge.net wrote: On 11/11/2012 02:22, Jon wrote: It's unfortunate you both had bad experiences with cmake. Cmake really is quite powerful, and recent syntax mods make it friendlier to use. For example, I contributed the