Re: [RaceIntoSpace-developer] [Raceintospace-developer] Questions for developers

[Krzysztof K. <k.k...@gm...>]

Eric & all,

I'm CC-ing this to raceintospace-developer, so it stays in archive.
Let's keep the discussion there, so others can join it.

On Thu, Jul 24, 2008 at 07:34:05PM -0700, Eric Conrad wrote:

> Yikes.  I had no idea that this hadn't been compiled in Windows
> before.  That's incredible.  Okay, challenge accepted.

It might have been, but I never heard of anyone trying :) It builds fine
using windows version of unix-compatible compiler toolchain (mingw -
minimalist GNU for windows).

> I'll start doing the research to get this working.  I'm not quite sure
> how this is going to work.  It's possible we'll have to seperate the
> Windows and Linux programming files.  It might even be probable, but
> I'll see what I can do.

It would be a good idea to keep changes 1) localized and 2) minimized
:) If needed, you can add files required only by the windows build to
os_win32 subdirectory. Probably you will have to provide a "project"
file for your build environment (compiler) of choice.

If many changes to some existing file are required, then it might be
easier to provide separate, OS-dependant functions in different source
files (say fs_linux.c for linux, fs_windows.c for windows etc)

> Conditional compilation.  I've never heard of that.  Does that mean it
> compiles under different rules with different conditions?  Meaning, compile
> like this in Linux, like that in Windows?  I'll have to look into that.

Conditional compilation depends on the C preprocessor. Say you have code:

  #ifdef CONFIG_BUILD_WIN32
     /* code for windows */
  #else
     /* code for anything else */
  #endif

This is self-explanatory, but you need to define (or not) the
CONFIG_BUILD_WIN32 somewhere. The "configure" script is responsible for
that, and the definitions go to the file "race.h". Once you #include
"race.h", then you have the configuration definitions accessible for
your code.

> I'll keep open communication with you.  Thanks for letting me know
> about some of those bugs.  I know there's people anxious to see them
> fixed.  So if I can compile this, I'll just start testing and see if
> it's worth releasing 0.4.7.

Some time ago I was fixing bugs, and Peyre was doing the
testing. Bugfixes went into CVS, but we have never released
0.4.7. I have some "private" builds for win32 hosted at
http://pleple.ict.pwr.wroc.pl/~files/, these include the bugfixes I
mentioned. So please make sure that bugs you're planning to fix are
still there :)

Regards,
-- 
Krzysztof Kościuszkiewicz
Skype: dr.vee,  Gadu: 111851,  Jabber: ko...@ja...
"Simplicity is the ultimate sophistication" -- Leonardo da Vinci