#How to prepare for release?

1 messages · Page 1 of 1 (latest)

tame tangle
#

In the "Included Files" folder there are plain text files and encrypted files (for release mode).

Is there a way to detect (maybe in the prebuild_step command script) or anywhere else, whether it's a release or a default compile?

I would be interested in getting the active configuration when the build started.

How do you prepare for a release? Do you have all your included files ... in the notes folder? anywhere else? and only copy these to the destination, that shall be part of the installer package?

Interested in any ideas, including igor command line arguments, how to best prepare the "included files" for release. some of the debug files simply may not be there in the release package.

wintry siloBOT
rocky rain
#

I keep on telling myself "Tab go write a tutorial" and then I end up not doing that haha

balmy belfry
#

Tab go write a tutorial

#

it's 2vs1 now

rocky rain
#

Oh no

#

But in all seriousness, there's a couple environment variables that are exposed, depending on the platform.
On Windows, you can use set to retrieve all of them. On MacOSX/Linux, you can use env.

In terms of configs, iirc you can use YYConfig to retrieve the current configuration used during building.

image.png
#

As for run vs release, most of the build scripts will run for either one

#

Except for the *_run_step and *_package_step

#

The run scripts are for running via the IDE, package is for exporting

tame tangle
#

YYConfig contains the name of the configuration? will test immediately - that's all I need ... everything else is done in the command script

rocky rain
#

I just checked

#

Lowercase c

#

YYconfig

tame tangle
#

is there a manual page of all invokable command scripts and when they trigger?

rocky rain
#

I tend to setup a quick batch script for like pre_build_step or something and have

set
pause
#

To collect all of the possible values

#

They do also difer depending on the build stage

#

Mainly post_textures and pre_project_step

tame tangle
#

okok we are definitely heading towards the right direction...
one last dumbo question, maybe you know it, then I don't need to try to find out: Are the Notes part of the compiled installer package? or are notes just "for the dev in the ide"?

rocky rain
#

Dev only

#

But you could copy them via batch if needed

tame tangle
#

no notes in output... this is PERFECT.
because files in the notes open with double click -- then i will move all my jsons to the notes and copy only those needed for each config in the prebuild batch

#

this is (for my current requirements) almost the perfect way

rocky rain
#

If it's for included files, I'm pretty sure you can choose which ones don't export per config

#

Or even entire platforms

#

Yeah

tame tangle
rocky rain
#

Right click -> Open Properties

#

Then look at the inspector

#

This is one of my files

#

And I can configure them per platform, per config

tame tangle
#

ohoh ooooooone moment... these checkboxes are PER CONFIG?

rocky rain
#

Yes

tame tangle
#

nifty - didn't think that's the case ok well then i just disable the encrypted in default and swap in release

rocky rain
#

nods

tame tangle
#

thanks -- very very fine solution

bows before the allmighty cat

rocky rain
#

No worries 😄

tame tangle
#

i still need to "compile" (i.e. compress and encrypt) my jsons in the release case but that's what the batch file is for -- i think i have all i need