FIFE forums

Please login or register.

Login with username, password and session length
Advanced search  


FIFE 0.4.0 has been released on 15th of January, 2017!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - vtchill

Pages: 1 ... 10 11 [12]
General discussion / Re: A new name for FIFE
« on: July 24, 2008, 06:39:57 am »
how about

Fast Insanely Flexible Engine


Flexible Insanely Fast Engine


Framework development / Re: Improving the scons build scripts
« on: July 24, 2008, 06:28:26 am »
I am working on modifying the build scripts and build structure a little bit.

I am currently thinking something like this for structure:

-- Root
   - SConstruct
   - src (engine source)
   - tests (unit test source files)
   - build
      - linux
         - bin
         - external (will hold things like UnitTest++ headers and lib)
      - win32
         - SConscript (possibly if there is enough commonality)
         - msvc2005
            - SConscript
            - bin
            - external
         - msvc2008
            - SConcript
            - bin
            - external
         - mingw
            - SConscript
            - bin
            - external
      - darwin (mac)   
         - SConscript
         - bin
         - external

The root level SConstruct will do some basic things like setup common paths and environment properties as well as figure out which platform specific SConscript file to run. The platform specific build environment properties can then be added/modified in the SConscript files for each platform.

This structure was just an initial thought and will almost definitely change some as I start trying to work through it. I am sure there are some problems and cases I am not thinking about.

Please post comments and let me know what you guys think.

I am planning to provide the msvc 2005 project for unit tests this week. I am also going to work on the scons+mingw support this week to try and get that up and running. I hope to have both done by the weekend.

I agree that 1.5 does offer some much needed improvements like easier merging of branches and better archiving of history.  I personally would wait until some larger projects move to 1.5 and see how the integration of their existing branches go.  Even on the subversion site they state that not all features are fully implemented and the better merging is still not fully operational.

In case we do decide to upgrade we just need to make sure everyone knows since some things are not compatible anymore.

Framework development / Re: new unit testing suite
« on: June 26, 2008, 11:35:40 am »
I haven't fully tested the single binary yet.  If it does yield the errors then I guess we will have no choice but separate executables.  I will report back when I have fully tested it.

Framework development / Re: new unit testing suite
« on: June 25, 2008, 10:45:11 am »
I think we should shoot for building all the unit tests into a single executable.  This is how unit tests are usually built so that it can easily be ran as a post build event. 

I would also vote for keeping the new  unit tests in the /tests folder just like the old ones.

Each supported IDE/compiler will need the appropriate setup/commands to first build FIFE as a static lib (.a or .lib) and then build the unit tests which will link to the static FIFE lib.  What directory should the FIFE static lib be put in?  Will this directory be different for different OS and/or IDE?

General discussion / Re: A new name for FIFE
« on: June 24, 2008, 01:00:58 pm »
I am definitely in favor of changing the acronym.  I think it will be good to broaden the scope of the project and distance the project from the Fallout name.  I don't really have a strong feeling for any of the names mentioned; I thought they were all good suggestions.

Framework development / Re: new unit testing suite
« on: June 24, 2008, 06:26:00 am »
I will probably have some time later this week to try and work on this.  I think we should be able go get this settled by the end of the week.  It might be helpful Barra if you posted a little list in this thread of exactly what needs to be done to get the tests fully integrated into FIFE just so we are all on the same page.

Framework development / Re: Guichan Upgrade
« on: June 16, 2008, 09:24:16 pm »
I should have more time tomorrow night to look into this problem and post a ticket on trac.

Introduce yourself / Re: Hello everyone
« on: June 15, 2008, 07:05:04 pm »

It is good to hear you are interested in the project.  I have just started helping out with it myself and so far it seems like a really well run project with great developers.

Feel free to grab the source code from the svn repository.  Tutorials and information on installation and compiling FIFE should be on the wiki page:

Also we have an IRC channel where most of the developers meet to discuss the project.  Here is a link to the information about the IRC channel:

Please post on the forums or come to the IRC channel if you are interested and/or have any questions.

Framework development / Re: Guichan Upgrade
« on: June 15, 2008, 06:55:26 pm »
Since I could get it to happen on my linux VM I will try and debug the problem.  As I said in an earlier post I am going to try the fullscreen on my windows box also and see if I can get the same problem.  I will post back with any results or fixes.

Is there a bug/ticket for this issue?

Framework development / Re: Guichan Upgrade
« on: June 14, 2008, 11:07:22 am »
I tried the new guichan and patch.  The island_demo would crash in the Engine::Init code and throw a FIFE::SDLException.

I am running on Ubuntu 8.04 inside of a virtual machine (parallels) on Mac os X.

I traced the problem back to the file inside of the island_demo directory.  The exception occurs when the fullscreen is set to 1.  When it is set to 0 everything runs fine.

I am going to try this out on my windows box later this weekend.

Framework development / Re: new unit testing suite
« on: June 10, 2008, 02:16:06 pm »
Putting it in a compiled SDK would be a good idea.  To redistribute it you only need to include the headers and the static lib to link against.

Framework development / Re: new unit testing suite
« on: June 09, 2008, 04:22:13 pm »
I am still looking over the build environment and am thinking about how to integrate building UnitTest++ into it.  I will have to run some tests on linux and windows to see if i can get it to build for both.  I will keep this post updated with my findings and I will also submit any patches to the ticket.

Also if any other developers have feelings on where the UnitTest++ src and lib should live please post your thoughts.  Any knowledge on how to integrate it into the build process would be helpful also.

Framework development / Re: new unit testing suite
« on: June 08, 2008, 06:41:51 pm »
I tested the patch NikN posted on a linux machine and all the tests passed except for the test_dat2++.cpp.  After a couple of minor fixes to the test_dat2++.cpp file all the tests passed.  I submitted my patch for the fix.  Just be aware that my patch has a lot of changes in it to facilitate building the tests and looking for the UnitTest++ directory in the /ext directory.  If you want to just see the changes to the test_dat2++.cpp file just let me know and I will give you just that file so you can do a simple diff on it.

The issue I wanted to bring up deals with where we want to actually put the UnitTest++ source code so we can link to it and where we want to put the static lib it generates.  Another issue is how we are going to build the UnitTest++ library.  The nice part about the library is that it provides both a makefile for building an archive (.a) file on linux and a visual studio solution for building a static library (.lib) on windows machines.  Please let me know what you guys think.

Pages: 1 ... 10 11 [12]