Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-05 Thread Javier Agustìn Fernàndez Arroyo
10 MB downstream ADSL right now, and will have a 50 MB downstream/5MB upstream optical fiber in a month I wanted to ask if i could take this bandwidth for ReactOS in some way. On Sun, Jun 5, 2011 at 4:55 AM, Adam geekdun...@gmail.com wrote: Same here. On Sun, 05 Jun 2011 06:28:32 +1000,

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-04 Thread Aleksey Bragin
For reference, I'm often located at the place where I only have 512 kbit/s internet connection. So please don't bloat the stuff too much. Thanks. Aleksey. On Jun 3, 2011, at 7:12 PM, Zachary Gorden wrote: The only developer I know who would be majorly impacted by increased BE download

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-04 Thread Adam
Same here. On Sun, 05 Jun 2011 06:28:32 +1000, Aleksey Bragin alek...@reactos.org wrote: For reference, I'm often located at the place where I only have 512 kbit/s internet connection. So please don't bloat the stuff too much. Thanks. Aleksey. On Jun 3, 2011, at 7:12 PM, Zachary Gorden

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-03 Thread Colin Finck
Zachary Gorden wrote: I object highly to the idea of bundling cmake with the BE. Most platforms already have binaries built of cmake, either by the distro or for Windows, the people who make cmake provide an installer. I don't see the point here, you could say exactly the same about every

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-03 Thread victor martinez
I am agree with Colin. The idea of having a Build Environment is not just to make the life easier to our devs, but also to have ISOs which we can compare. If the Environment doesnt bundle *ALL* the tools, then we can have devs/testers with different Tools combinations...it can lead to break

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-03 Thread Jérôme Gardou
Guess what... Cmake provides such a GUI Le 03/06/2011 12:26, victor martinez a écrit : I am agree with Colin. The idea of having a Build Environment is not just to make the life easier to our devs, but also to have ISOs which we can compare. If the Environment doesnt bundle *ALL* the tools,

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-03 Thread victor martinez
Does Cmake provide a GUI which: 1)Updates the local copy to any desired revision? 2)Which changes the Architecture to build ReactOS for the current session? 3)Fully clean the source directory/logs? :) Date: Fri, 3 Jun 2011 12:32:41 +0200 From: jerome.gar...@laposte.net To: ros-dev@reactos.org

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-03 Thread Timo Kreuzer
Am 03.06.2011 12:31, schrieb Adam: I wonder if the CMake Gui can be used here. Have had a bit of a play with it but I'm not sure how it is possible to make it friendly for RosBE users so they don't have to linux around with the config and all that. I've been using the cmake gui quite often

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-03 Thread Zachary Gorden
@Ged The user is able to choose which BEs they want to install, so if they only want the x86 BE, they can deselect the x64 or ARM features. That's a pretty standard functionality of MSI after all. @Daniel If that's the route being taken, you're going to have to go with #2. You can't run 2 MSIs

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-03 Thread Timo Kreuzer
Am 03.06.2011 16:46, schrieb Zachary Gorden: @Ged The user is able to choose which BEs they want to install, so if they only want the x86 BE, they can deselect the x64 or ARM features. That's a pretty standard functionality of MSI after all. Just to be clear, we are talking about 1,5 hours

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-03 Thread Zachary Gorden
The only developer I know who would be majorly impacted by increased BE download size is Eric. Eric, any comments on this topic? On Fri, Jun 3, 2011 at 10:03 AM, Timo Kreuzer timo.kreu...@web.de wrote: Am 03.06.2011 16:46, schrieb Zachary Gorden: @Ged The user is able to choose which BEs

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-02 Thread Zachary Gorden
I object highly to the idea of bundling cmake with the BE. Most platforms already have binaries built of cmake, either by the distro or for Windows, the people who make cmake provide an installer. We provide the compilers and linkers and we provided rbuild because it was our own thing, but cmake

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-02 Thread Jérôme Gardou
Fact is that we currently use the bleeding edge fersion of cmake, and we may be ahead of it. And it's not that big actually. Le 03/06/2011 00:01, Zachary Gorden a écrit : I object highly to the idea of bundling cmake with the BE. Most platforms already have binaries built of cmake, either by

Re: [ros-dev] 1296 [dreimer] Get the cmake path from a system variable called _ROSBE_CMAKEPATH. Hard coding is eeevul!

2011-06-02 Thread Zachary Gorden
Bleeding edge? As far as I'm aware of on Windows we just tell people to go install the latest stable version. If the situation on Linux is different then you have a reason to need to bundle. On Windows we don't. 2011/6/2 Jérôme Gardou jerome.gar...@laposte.net Fact is that we currently use