On Fri, Jun 27, 2014 at 2:19 PM, gettimothy <gettimothy@zoho.com> wrote:

HI Eliot and Tim.

Makes sense to me. What I am trying to figure out is the best way to generate it at compile time and ditch the hard-coded configH method per the requirements.

One option is to just invoke configure per the build.linuxXYZ/build/mvm file as the source tree is identical.

Would that be a problem?

Well, if you're doing CMake then you'll want to use whatever CMake uses to generate config.h. platforms/unix/conf/configure runs automake.

Another possibility is in Ian's CMake system for the Standard Interpreter, it is generated by hand.

Even if configure was generated by automake its input files (configure.in et al) were not ;-)

One could see that inputs to CMake are hand-written as an advantage of CMake, it getting one further in each step. autoconf's generating configure is problematic, configure itself needing to be generated on the right system (generating it on Mac OS X for example produces a completely broken configure)..

svn co http://squeakvm.org/squeak/trunk squeak
cd squeak
mkdir bld
cd bld
../platforms/unix/cmake/configure
make

Looking at that /platforms/unix/cmake/configure file, it is just a shell script with some hard-coded definitions/flags.

What I could do is dynamically create that ../platforms/unix/cmake/configure script from the class. Then in the build script build.sh invoke that script first before invoking cmake.

I do think the first option is easier.

Thoughts?

thx.

tty

--
best,

Eliot