언어 설정

Menu
Sites
Language
Build project from CLI with build configs from IDE

Good day

I'm having trouble building my project from the CLI.  From what I understand I have to create a separate build config for the CLI and cannot use the existing build configurations I've created for the IDE.  This feels like double work to maintain and was wondering if there is a simpler way to make use of the existing build configs in order to set up a build server which uses the project settings like it would on my IDE while developing.

I've, as an interim, tried to use the command line generated from the IDE's config and simply running clang++ with the options to see if it works, but in normal Command Prompt, the input buffer isn't long enough, in PowerShell, I keep getting argument errors, and in Ubuntu (using WLS) I've installed the CLI version of Tizen Studio, but it doesn't contain LLVM, and trying to install it with sudo apt-get install -y llvm-4.0 says it can't find the package.

(output from PowerShell)

At line:1 char:668
+ ... ram=ssp-buffer-size=4 -mlittle-endian -mfloat-abi=softfp -Wl,--hash-s ...
+                                                                 ~
Missing argument in parameter list.
At line:1 char:689
+ ...  -mlittle-endian -mfloat-abi=softfp -Wl,--hash-style=gnu -Wp,-D__SOFT ...
+                                                                 ~
Missing argument in parameter list.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : MissingArgument

I'm guessing I could have dug a little deeper before asking, but thought I'd put this out there while figuring out how to go about it.  This is somewhat new territory for me.

Thanks in advance.

목록

Responses

2 댓글
de Villiers

To date I have resorted to export the config with the "Export to CLI project" option when right-clicking on the project in the IDE, but there's still problems with this.  In order to get the project building I still need to fix things in the `project_def.prop` file, and actually manually point to the Knox SDK libraries, as it doesn't find them, no matter what I try with the -r and -f switches for rootstraps and frameworks.

Perhaps I can live with these workarounds, at least I can build and sign and package my project, but I still have the problem that, I have multiple build configs, depending on the requirements.  When "exporting to CLI project", I only appear to have Debug and Release, and nowhere can I even see what the configurations for each are, or adjust it, nevermind create my own.

Any advice on that?  Worthy of a new topic rather, perhaps "Configuring build configs when building with CLI"?