Compilation successfull but cant start.

[rickg22]

Yiannis, I think we DO need a "make install" target for linux so iit will run the ./update script.

[mandrav]

IIRC, what we DO have is a 'make update' target (calls 'update').
'make install' is a whole other issue, since it would be expected to install C::B in the user's machine...

Yiannis.

[rickg22]

okay.... anyway i think the update should be run automatically...

[grv575]

It does as of the latest cvs.

[rickg22]

cool!

[zieQ]

Maybe it's not a good idea to do it automatically. If you write some bugs while developing with the /output version and hit compile, you will never be able to make it work back after the update. This should be called manually IMHO.

Or better separate in the update
- the copy/zip of the resources
- the copy to output dir

maybe update-res and update-out and update-res called automatically.

[grv575]

Yes, but if you write some bugs in the source, then you are going to need a backup of that source anyway to revert to.  So just build that version...

[zieQ]

Not exactly a backup but a bug fix. And that's not really the same for me :p

[grv575]

OK, so CVS HEAD does not run update automatically (but I like it better this way.  it's easy enough to select the update target and hit compile...and this way it's easier to isolate bugs as the edit/compile cycle is shorter).  If you do want it to run auto, then edit project->properties update target and set it to 'build this target with "all"'.