31
When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.
cmd /c MakePackageRelease.cmd
[Window Title]
codeblocks.exe
[Content]
You must select a host application to "run" a commands-only target...
[OK]
Uhm, well... not really.
The history looks like you cherry-picked the commit, that was the worst option (does the GitHub UI even offer that option?). In general you perform a merge, for external contributions i prefer to always enforce a merge, even if like in this case a fast-forward merge would have been possible.
Also, it is kind of bad practice to create a PR from the main branch, in general you make a feature branch and create a PR from that one.
Hi Tim,
I tested the plugin in Linux wx3.0, it works fine. I've created pull request https://github.com/stahta01/GitBlocks/pull/1 with project file. Could you please check?
Thanks,
Christo
Looks like what I'm gathering is that you can't build a single project on the command line and have it figure out the dependent projects, and then build those. Workspace builds work because it has knowledge of all other projects. Command line looks like you need to specify each individual project, in the order you want, to create the final executable.
I found the attached on the code::blocks wiki, but after setting up the external dependencies in the project, it's still not working on the command line.
Building the workspace works, but that doesn't work on the build machine because we don't save/have a workspace in the build system.
Code::Blocks is open-source, published under the GNU GPL, so you are more than allowed to use screenshots of it in publication, as far as I understand.