Raydium 3D Game Engine

Official forum for everything about Raydium, ManiaDrive, MeMak, ...
It is currently Thu Dec 14, 2017 4:45 pm

All times are UTC




Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: Path organisation
PostPosted: Sun Oct 12, 2008 3:32 pm 
Offline

Joined: Sun Oct 09, 2005 10:46 pm
Posts: 759
Hello,

I'm in trouble :shock:

It's allways problematic to make a distrib of a raydium appli.

I work on several raydium appli, (vincente, andygfx and several home projects).

All of them are in a separate directory. With data file and project files and whatever they need in this directory or sub directory.

Execution runs in a common bin directory (i don't want to have n bin directorys, and i can't set all dll in the system as it is more problematic to check dll dependency).

I can't have a data in my bin directory or, andygfx data will be merged with vincente one for example. And it will be impossible to separate them.

Now with this organisation: releasing an app is pain.

For exemple if i forget to change path from ../versusrx to . (vincent :( )

How do all of you organise your work ? Any clue ?

Is there a better way ?

Have a nice day
Ouille.


Top
 Profile  
 
 Post subject: Re: Path organisation
PostPosted: Sun Oct 12, 2008 4:22 pm 
Offline

Joined: Tue Jul 08, 2008 2:37 am
Posts: 181
ouille wrote:
I don't want to have n bin directorys, and i can't set all dll in the system as it is more problematic to check dll dependency.
Regarding to the DLL location: Isn't it possible to have all dependencies in one directory, e. g. the folder from the SDK and only create a symbolic link or alias - whatever it is called under Windows to share the files, so you're able to work and test the application outside the mainline production?

Hope this is useful for you, I'll give a short view about my handling object procedure:
- All Raydium dependencies are located globally in /opt/raydep/*/{i386,ppc,universal}/{include,lib}.
- Application directory contains an alias locally to the needed dependencies, e. g. "ln -s /opt/raydep/*/universal/* ." under *nix.
- On package progress the links are resolved to the real files whenever needed.

Regarding to the data path settings, I'm not using a bin folder for my binaries, so I'm able to use raydium_path_add("Resources"); after the Raydium initialization, because Raydium automatically changes to the right directory, where the files are located "*.app/Contents/{MacOS/Binary,Resources/Data.*}".

I hope this is helpful for you, since I don't really understand what do you want to do. :roll:


Top
 Profile  
 
 Post subject: Re: Path organisation
PostPosted: Sun Oct 12, 2008 4:35 pm 
Offline

Joined: Sun Oct 09, 2005 10:46 pm
Posts: 759
Hello,

I dream of working links on windows.

But ...

Link's on windows are not handled the same way's by all application. Some of them saw a link as a file !

For the rest it sound like one bin for one app, it's more elegant with links.

I'll try to tests links more further.

Thank's for the informations.

Have a nice day
Ouille.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group