Export vs build in the Terminal

[ustk]

Is there a way to make the binary not compile (or to compile again if disabled) by the command line tool when exporting a project? Maybe with a certain flag?
Or is this default behaviour engraved in the universe's frame forever?

EDIT: This is about the Terminal and not the command-line tool that I badly mixed up in my head...

[d.healey]

@ustk I don't quite understand your question but if you use the --help flag you can see all options available.

HISE Command Line Tool
----------------------

Usage: 

HISE COMMAND [FILE] [OPTIONS]

Commands: 

export: builds the project using the default settings
export_ci: builds the project using customized behaviour for automated builds
 - always use VisualStudio 2017 on Windows
 - don't copy the plugins to the plugin folders
 - use a relative path for the project file
Arguments: 
FILE      The path to the project file (either .xml or .hip you want to export).
          In CI mode, this will be the relative path from the current project folder
          In standard mode, it must be an absolute path
-h:{TEXT} sets the HISE path. Use this if you don't have compiler settings set.
-ipp      enables Intel Performance Primitives for fast convolution.
-l        This can be used to compile a version that runs on legacy CPU models.
-t:{TEXT} sets the project type ('standalone' | 'instrument' | 'effect' | 'midi')
-p:{TEXT} sets the plugin type ('VST' | 'AU' | 'VST_AU' | 'AAX' | 'ALL')
          (Leave empty for standalone export)
-a:{TEXT} sets the architecture ('x86', 'x64', 'x86x64').
          (Leave empty on OSX for Universal binary.)
--test [PLUGIN_FILE]
Tests the given plugin

set_project_folder -p:PATH
Changes the current project folder.

set_hise_folder -p:PATH
Sets the location for the HISE source code folder.
get_project_folder
Returns the current project folder.

set_version -v:NEW_VERSION_STRING
Sets the project version number to the given string

clean [-p:PATH] [-all]
Cleans the Binaries folder of the given project.
-p:PATH - the path to the project folder.

create-win-installer [-a:x64|x86] [-noaax] [-rlottie]
Creates a template install script for Inno Setup for the project
Add the -noaax flag to not include the AAX build
Add the -a:x64 or -a:x86 flag to just create an installer for the specified platform

create-docs -p:PATH
Creates the HISE documentation files from the markdown files in the given directory.
load -p:PATH

Loads the given file (either .xml file or .hip file) and returns the status code
You can call Engine.setCommandLineStatus(1) in the onInit callback to report an error

compile_networks -c:CONFIG
Compiles the DSP networks in the given project folder. Use the -c flag to specify the build
configuration ('Debug' or 'Release')

[ustk]

@d-healey Well maybe I don't explain correctly or I don't know how to use this...

The scenario is when I Export As Standalone in Hise, after going through the modals the Terminal opens up and the export begins.
Here Hise exports the files that are necessary (like the Jucer and consort), and I want it to stop there.
Because after that the compilation begins, but in certain cases, I need to edit the jucer first and compile through Xcode.

Of course, I can just terminate the terminal process, but is there a way to prevent this to happen?

[d.healey]

@ustk

but is there a way to prevent this to happen?

Use GNU/Linux it doesn't happen here

If you use the command line tool I believe it just generates the jucer file and you have to do the rest - try it and see.

If that doesn't work it should be very easy to prevent it starting the compilation in the HISE source code.

[ustk]

@d-healey Yeah thanks. I imagine there should be a flag somewhere I could set from within the project's preferences

[d.healey]

@ustk Or you could customise the jucer template so it always generates it with your preferred settings.

[Christoph Hart]

I‘m aborting the compilation to edit the project in XCode since 2013 and I‘m still alive.