World: r3wp

CMake Input is a "CMakeLists.txt" file, which is written in "just 
another Makefile language".

Yes, but the ARM make tool looked like 1982 the last time I tried 
it.

No idea what you tried, but you'd typically just use GNU make on 
ARM as well.

Have you tried using the makefile on BSD or OSX?

No, as there is no hostkit release for either of those.

Basically, same as Linux right now.

Can't sensibly try without e.g. a OSX dylib.

But I prodded you for weeks to build one :)

Also, problematic builds are Sun and HP Unix. But, anyway, if people 
are willing to add them, it's ok with me.

Right... I remember that now. We'll have to give it another go.

I guess sticking with the big three (+ BSD, maybe) will be sufficient 
for now.

here's the CMakeLists.txt from the OpenCV project , as an example:


https://code.ros.org/svn/opencv/tags/latest_tested_snapshot/opencv/CMakeLists.txt

In my opinion, there are bigger problems to tackle before spreading 
thin over multiple platforms makes sense.

(Eventing, for example)

Yes, of course, but if more developers get involved, the work does 
not need to be sequential.

Oh yeah ..let's get an Os/2 build too !

Hmmm.

http://bolka.at/2010/rebol3/CMakeLists.txt.html

Looking at above link, I don't think cmake provides much benefit 
to us.

( the current version of Os/2 is ecomworkstation  and is positioned 
as a secure enterprise client environemnt )

Here's the CMake buildfile I use for the A96 hostkit

CMake provides the benefit that we don't have to reinvent the wheel 
for now. It has, for example, a nice installer for Win32 and can 
automatically generate Visual Studio project files from the above.

well, if you are considering a makefile generator, at least cmake 
is somewhat of a standard

Installer? What does it install?

cmake.exe

CMake takes the above as input and generates e.g. a Makefile as output.

Taking specifics of the actual build environment into account.

The method I use for R3 simply uses REBOL to generate the host-kit, 
the makefile, and other related files at the same time.

With CMake the workflow of a user who wants to build the hostkit 
on Win32 would be as follows:
- Download and install a toolchain (e.g. MingW or MSVC)
- Download and install CMake
- Download the R3 Hostkit

- Generate a R3 build script for your preferred toolchain using CMake. 
E.g. use CMake to generate a GNU make Makefile for MingW
- Build the R3 Hostkit (using the generated build script)

Without CMake, those steps would be the same, except for the extra 
installation of CMake and the generation of a local build script. 
But it would also either limit the user to a single toolchain (such 
as MingW, currently) or you would need to replicate some of the functionality 
of CMake in your make-build.r

there's a GUI front end for cmake too, though I guess one could be 
made for REBOL just as easily - this lets you resolve env var issues 
and other things

Further, at least for the A96 hostkit, Linux and Win32 hostkits are 
completely separate packages, and that's an incredible nuisance for 
someone doing cross-platform work.

It built for me just fine but I had to modify the makefile to use 
cp lib\r3lib.dll .
instead of 
copy lib\r3lib.dll . 
inside a mingw cmd window.

Do we have a test files to run to check if all areas of R3 that is 
implemented is working?

It would be good if we had access to the test suites

After adding MinGW\bin and msys\1.0\bin to the windows command path 
and also copying rebol.exe to msys\1.0\bin folder, I was able to 
build it from a normal command window without modifying the makefile.

Carl: in any case, I don't care much about CMake. Just shipping the 
hostkit with your make-build.r instead of a pre-built makefile would 
most likely do just fine for getting an integrated cross-platrform 
build working. (Plus, of course, bundling the libraries and sources 
for all platforms in the hostkit.)

I see go.r can be use as test.

And just in case: _THANKS_ a million for the new hostkit code drop, 
Carl (and everyone else who helped make it happen)!

echo that

yes thanks to everyone who worked on making it happen.  :-)

we now have a domain ( thanks Andreas ) for the tracker http://jira.rebolsource.net:8080/secure/Dashboard.jspa

and now is probably as good a time as any to move this discussion 
to !REBOL3 Host Kit

+1 Thank you!

Apart from Win, OS-X, Linux, BSD, the next most important platform 
is really imo an ARM plus Android.

Put Arm before BSD

BSD is well serviced by R2

I agree - for R3 to gain traction, mobile support should be a priority.

Jira: Why a new tracker? Isn't CureCode still be used? No information 
fragmentation please.

Priorities: Before getting new platforms up & running I see feature 
completion to be more critical. Otherwise we have a moving target 
that takes to much effort to keep in sync.