Author Topic: AGS 3.3.x/3.4.0.0 Developer Discussion  (Read 45462 times)

monkey0506

  • SEND PIZZA.
    • Best Innovation Award Winner 2017, for his work to help AGS games reach the widest possible audience - through popular distribution platforms (Steam, Galaxy) as well as other operating systems (Android, Linux)
    • monkey0506 worked on one or more games that won an AGS Award!
    •  
    • monkey0506 worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #180 on: 28 Oct 2014, 23:33 »
The .user file was not, in fact, my idea. 8-) It was implemented by CJ around AGS 3.0.2:

Quote from: Pumaman
Quote from: monkey_05_06
Edit: BTW Chris, what is this Game.agf.user file that seems to have cropped up?

It's for storing any settings that are specific to you (the user of the AGS Editor) and not game settings.
At the moment it's only used to store source control information, but in future it might also contain which windows you had open when you closed the editor, etc.

Based on this, I would say it makes sense to keep this type of info in that file (since it's not really project data).

Gurok

  • Rottwheelers
  • When life hands you lemons, combine them with the mop
    • I can help with AGS tutoring
    • Best Innovation Award Winner 2016, for improving and extending the AGS scripting language
    • I can help with proof reading
    • I can help with scripting
    • Gurok worked on one or more games that won an AGS Award!
    •  
    • Gurok worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #181 on: 28 Oct 2014, 23:58 »
The .user file was not, in fact, my idea. 8-) It was implemented by CJ around AGS 3.0.2:

Quote from: Pumaman
Quote from: monkey_05_06
Edit: BTW Chris, what is this Game.agf.user file that seems to have cropped up?

It's for storing any settings that are specific to you (the user of the AGS Editor) and not game settings.
At the moment it's only used to store source control information, but in future it might also contain which windows you had open when you closed the editor, etc.

Based on this, I would say it makes sense to keep this type of info in that file (since it's not really project data).

Oh fantastic. Thanks, Monkey.

Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #182 on: 31 Oct 2014, 21:44 »
Mhh so now there are tags called v.3.4.0.0 and v.3.4.0.1 in the development branch. That's super confusing. What will be the version of the next stable release?

If there are no version numbers reserved for development releases as in my suggestion then a version like 3.4.0.0 sounds like a stable release and all development versions before that can only be called 3.4.0.0-alpha1, 3.4.0.0-alpha2, 3.4.0.0-beta1 etc. Remember that version numbers should increase so you can't go back from 3.4.0.1-alpha1 to 3.4.0.0.

Also the tags don't have an "alpha" so they look like stable releases.
« Last Edit: 31 Oct 2014, 21:46 by BigMc »

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #183 on: 31 Oct 2014, 23:35 »
Mhh so now there are tags called v.3.4.0.0 and v.3.4.0.1 in the development branch. That's super confusing. What will be the version of the next stable release?
It will be 3.4.0.something.

Also the tags don't have an "alpha" so they look like stable releases.
Okay, I'll add alpha to them.

Gurok

  • Rottwheelers
  • When life hands you lemons, combine them with the mop
    • I can help with AGS tutoring
    • Best Innovation Award Winner 2016, for improving and extending the AGS scripting language
    • I can help with proof reading
    • I can help with scripting
    • Gurok worked on one or more games that won an AGS Award!
    •  
    • Gurok worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #184 on: 01 Nov 2014, 14:45 »
What's Release_MD in the build configuration list for the editor?

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #185 on: 01 Nov 2014, 14:51 »
What's Release_MD in the build configuration list for the editor?
It uses /MD compilation flag for Common and Compiler static libraries, which tells them to link runtime C++ library dynamically, as opposed to /MT which links them statically.
I had to change to /MD after we started to use STL, otherwise Common.lib caused linker errors when linking to AGS.Native.
/MT is still used for the engine.

Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #186 on: 02 Nov 2014, 07:51 »
Now the tags are:

3.4.0.0-alpha1
3.4.0.1-alpha2

You can get rid of either of the last two numbers. Either

3.4.0.0-alpha
3.4.0.1-alpha

or

3.4.0-alpha1
3.4.0-alpha2

would be fine. Or am I missing something? I like the last variant better.

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #187 on: 02 Nov 2014, 13:27 »
Now the tags are:

3.4.0.0-alpha1
3.4.0.1-alpha2

You can get rid of either of the last two numbers. Either

3.4.0.0-alpha
3.4.0.1-alpha

or

3.4.0-alpha1
3.4.0-alpha2

would be fine. Or am I missing something? I like the last variant better.

The last number defines the consequent index of release. So it may be:
3.4.0.1-alpha
3.4.0.2-alpha
...
3.4.0.10-alpha
3.4.0.11-beta
...
3.4.0.25-rc
3.4.0.26-final
3.4.0.27-hotfix

Having all 4 numbers would be easier for me to understand its position in the history. So I'd rather keep it.
« Last Edit: 02 Nov 2014, 13:29 by Crimson Wizard »

Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #188 on: 02 Nov 2014, 14:11 »
Ok but I thought we wanted to get rid of the final and hotfix suffices. So no suffix would correspond to a stable release.

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #189 on: 02 Nov 2014, 18:12 »
Ok but I thought we wanted to get rid of the final and hotfix suffices. So no suffix would correspond to a stable release.
IIRC the problem I was addressing was that I was naming releases with suffixes only (e.g. 3.3.0-hotfix1, 3.3.0-hotfix2), instead of increasing visible version number.
As I see this, the numbers define unique index of the version, while suffix is an auxiliary description.

Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #190 on: 03 Nov 2014, 09:40 »
Ok I'll keep quiet as long as the versions are strictly increasing. :) I find this scheme much more weird than what I proposed though. :-D

monkey0506

  • SEND PIZZA.
    • Best Innovation Award Winner 2017, for his work to help AGS games reach the widest possible audience - through popular distribution platforms (Steam, Galaxy) as well as other operating systems (Android, Linux)
    • monkey0506 worked on one or more games that won an AGS Award!
    •  
    • monkey0506 worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #191 on: 10 Nov 2014, 23:33 »
Just saw that my pull request for building Linux got approved. :-D

Is there any specific timeframe as to when the next alpha/beta version is expected? I know there's been some pretty significant changes since 3.4.0.1, so it would be good to have an "official" build for people to test out these new features. ;-D

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #192 on: 11 Nov 2014, 01:10 »
Is there any specific timeframe as to when the next alpha/beta version is expected? I know there's been some pretty significant changes since 3.4.0.1, so it would be good to have an "official" build for people to test out these new features. ;-D
No, no specific timeframe, I am rather using "weight" of accumulated changes as a reference. And yes, I was going to make a new build, maybe in several hours.

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #193 on: 11 Nov 2014, 11:37 »
Say, how do you make the Linux folder for the editor? What it consists of? Are there any specifications?
How do I build the linux binaries for 32-bit and 64-bit? Maybe some instruction exists?

Can I take it from this archive, or linux binaries must be rebuilt anew?
« Last Edit: 11 Nov 2014, 11:44 by Crimson Wizard »

Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #194 on: 11 Nov 2014, 12:27 »
It's built using the script debian/make_ags+libraries.sh on Debian or Ubuntu (see comments in the file for instructions) and of course it should be built with the latest code if you want to make a release.
« Last Edit: 11 Nov 2014, 12:29 by BigMc »

monkey0506

  • SEND PIZZA.
    • Best Innovation Award Winner 2017, for his work to help AGS games reach the widest possible audience - through popular distribution platforms (Steam, Galaxy) as well as other operating systems (Android, Linux)
    • monkey0506 worked on one or more games that won an AGS Award!
    •  
    • monkey0506 worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #195 on: 11 Nov 2014, 13:28 »
Yes, it's just the folders/files that the make_ags+libraries.sh script produces (copy the data folder, sans any game files). I can do a fresh build this afternoon if needed.

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #196 on: 11 Nov 2014, 17:51 »
Yes, it's just the folders/files that the make_ags+libraries.sh script produces (copy the data folder, sans any game files). I can do a fresh build this afternoon if needed.
Yes, please.
I am getting some errors for "cowbuilder" thing, I'll need more time to understand how all this works.

Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #197 on: 11 Nov 2014, 19:09 »
Which errors? Did you follow the instructions?

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #198 on: 11 Nov 2014, 19:40 »
Which errors? Did you follow the instructions?
I followed them up to the
Quote
# Create the (chroot) environments that will be used for building ags:

# cowbuilder-dist wheezy i386 create
# cowbuilder-dist wheezy amd64 create
I do not really understand what this means. Are they the exact commands I should type, or I must also add some custom parameters here?
When I ran the first one, I get this:
Quote
ikm@ubuntu:~/git/ags$ cowbuilder-dist wheezy i386 create
 -> Invoking pbuilder
  forking: pbuilder create --logfile /home/ikm/pbuilder/wheezy-i386_result/last_operation.log --othermirror deb http://security.debian.org wheezy/updates main contrib non-free|deb http://ftp.debian.org/debian wheezy-updates main contrib non-free|deb http://ftp.debian.org/debian wheezy-proposed-updates main contrib non-free --debootstrapopts --keyring=/usr/share/keyrings/debian-archive-keyring.gpg --components main contrib non-free --debootstrapopts --arch=i386 --buildplace /home/ikm/pbuilder/wheezy-i386-base.cow --mirror http://ftp.debian.org/debian --architecture i386 --distribution wheezy --no-targz --extrapackages cowdancer
W: /home/ikm/.pbuilderrc does not exist
I: Logging to /home/ikm/pbuilder/wheezy-i386_result/last_operation.log
I: Running in no-targz mode
I: Distribution is wheezy.
I: Building the build environment
I: running debootstrap
/usr/sbin/debootstrap
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
E: Release signed by unknown key (key id 6FB2A1C265FFB764)
E: debootstrap failed
W: Aborting with an error
pbuilder create failed
  forking: rm -rf /home/ikm/pbuilder/wheezy-i386-base.cow

Re: AGS 3.3.x/3.4.0.0 Developer Discussion
« Reply #199 on: 12 Nov 2014, 05:08 »
I don't know why the key is missing but
http://marek.php5.sk/?p=150