Author Topic: [RELEASE] Yet Another Launcher 0.3 RC2, fully functional for windows and linux  (Read 43358 times)

0 Members and 1 Guest are viewing this topic.

Re: [RELEASE] Yet Another Launcher 0.3 RC2, fully functional for windows and linux
1. You are reading this right.

2. How is it possible to personalize it? Does it require to modify the code some how or is there some configuration file that can be modified before or after compilation?

3. As far as I understand, all the pilot profiles are saved inside ~/.fs2_open, which means that each TC will erase or will have access to the profiles of the previously ran TC. In the former case the problem is obvious and in the later case if the profiles have a different structure, maybe the game will crash or the existing profiles will get corrupted. As I am discovering the game, I am just guessing what will be the behavior.
Luke, use the F.O.S.S.!!!

 

Offline chief1983

  • Still lacks a custom title
  • Moderator
  • 212
  • ⬇️⬆️⬅️⬅️🅰➡️⬇️
    • Skype
    • Steam
    • Twitter
    • Fate of the Galaxy
Re: [RELEASE] Yet Another Launcher 0.3 RC2, fully functional for windows and linux
TCs should probably for now be installing a different binary which uses a different .data folder.  I believe that's still the recommended approach anyway.
Fate of the Galaxy - Now Hiring!  Apply within | Diaspora | SCP Home | Collada Importer for PCS2
Karajorma's 'How to report bugs' | Mantis
#freespace | #scp-swc | #diaspora | #SCP | #hard-light on EsperNet

"You may not sell or otherwise commercially exploit the source or things you created based on the source." -- Excerpt from FSO license, for reference

Nuclear1:  Jesus Christ zack you're a little too hamyurger for HLP right now...
iamzack:  i dont have hamynerge i just want ptatoc hips D:
redsniper:  Platonic hips?!
iamzack:  lays

 

Offline Havner

  • 26
Re: [RELEASE] Yet Another Launcher 0.3 RC2, fully functional for windows and linux
Download YAL sources, read the readme, it's explained there. Different qmake config options compile time. There is even script for that.

As for the home folder, yes, you're right. I wrote about that in gentoo bugzilla. Thing is, that this is not only about YAL, it's also about fs2_open where I have no influence where and how someone might patch his fs2_open to store config files/pilots.

As Chief said and as I described on gentoo bugzilla it's recommended to have a different binary for every TC. The above mentioned configurations for YAL change the path it looks for user config dir. But you _need_ corresponding fs2_open binary patched to use the same folder as well for it to work.
Need a linux launcher? Check here.

 
Re: [RELEASE] Yet Another Launcher 0.3 RC2, fully functional for windows and linux
I have just downloaded the source of YAL 0.3 RC 2, but I don't see in the README any reference to qmake :(.

To have the launcher "compliant" with TBP shouldn't I simply execute the following lines from build-all.sh:

Code: [Select]
./autogen.sh yal.pro "CONFIG+=tbp"
make -j2 release
make clean
Luke, use the F.O.S.S.!!!

 

Offline Havner

  • 26
Re: [RELEASE] Yet Another Launcher 0.3 RC2, fully functional for windows and linux
Yeah, it seems I simplified readme at some point when I added this script. But that's exactly what are you looking at, the CONFIG stuff. Have a look at yal.pro what it does and in the source code. GameInfo.cpp f.e.
Need a linux launcher? Check here.

  

Offline carn1x

  • 25
Re: [RELEASE] Yet Another Launcher 0.3 RC2, fully functional for windows and linux
Not entirely sure what I should do after compiling. I'm guessing I need to run yal.pro?

If so, my output is:
Code: [Select]
$ ./yal.pro
./yal.pro: line 5: TEMPLATE: command not found
./yal.pro: line 6: CONFIG: command not found
./yal.pro: line 7: DEPENDPATH: command not found
./yal.pro: line 8: INCLUDEPATH: command not found
./yal.pro: line 10: DESTDIR: command not found
./yal.pro: line 16: TARGET: command not found
./yal.pro: line 17: RESOURCES: command not found
./yal.pro: line 19: btrl: command not found
./yal.pro: line 20: TARGET: command not found
./yal.pro: line 21: RESOURCES: command not found
./yal.pro: line 22: DEFINES: command not found
./yal.pro: line 23: syntax error near unexpected token `}'
./yal.pro: line 23: `}'