[bug] command line building option -cleanBuild clean the different configuration

[lpcware]

Content originally posted in LPCWare by tinyusb on Mon Apr 21 21:47:24 MST 2014
Hi there, while working lpcxpresso command line http://www.lpcware.com/content/faq/lpcxpresso/building-projects-command-line?destination=node%2F1107.... I found out that the -cleanBuild option disregard the configuration passed from command line as follows:
- it will clean the current active configuration (I guess) in the project
- however still build the correct configuration passed from command line.

for example

---

Quote:

lpcxpressoc -nosplash --launcher.suppressErrors -application org.eclipse.cdt.managedbuilder.core.headlessbuild -cleanBuild my_project/config1 -data C:/my_workspace

---

will clean other configuration and build the config1 of my_project, this can be monitored via the console output.
my lpcxpresso version is 7.0.0

[lpcware]

Content originally posted in LPCWare by tinyusb on Tue Apr 22 02:47:47 MST 2014

---

Quote: lpcxpresso-support
Works perfectly for me with 7.1.1.

---

Glad to hear you fix that in 7.1.1, I will try to update later on and
alter the configuration a few times to test with.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Apr 22 02:41:53 MST 2014
Works perfectly for me with 7.1.1.

[lpcware]

Content originally posted in LPCWare by tinyusb on Tue Apr 22 02:02:11 MST 2014
I am sorry for not giving out any sense previously. This example should be easier to understand, here I use the cmsis project of lpc800 which has 2 build configuration Release and Debug. And I execute the command that I expect it to clean then build (rebuild) the project with Release configuration.

---

Quote:
C:\Users\hathach\Dropbox\tinyusb\workspace\tinyusb\demos>C:\nxp\LPCXpresso_7.0.0_92\lpcxpresso\lpcxpressoc -nosplash --launcher.suppressErrors -application org.eclipse.cdt.managedbuilder.core.headlessbuild -cleanBuild CMSIS_CORE_LPC8xx/Release -data C:\Users\hathach\Dropbox\tinyusb\workspace7

---

However, the console out indicates that it clean the Debug configuration instead. if I re-enter the command again, it will not rebuild the Release configuration (obviously since it clean the wrong configuration). I hope these would make a bit more sense.

[img]http://www.lpcware.com/system/files/cleanbuild_0.png[/img]

[img]http://www.lpcware.com/system/files/cleanbuild2.png[/img]

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Apr 22 01:27:15 MST 2014
Sorry, but I have no idea what you are talking about.

Please provide an example project that shows the problem, together with instructions on how to reproduce it.

[lpcware]

Content originally posted in LPCWare by tinyusb on Tue Apr 22 00:20:51 MST 2014
yes, I try to clean then build the "config1". Let's say the project has the standard "Release" & "Debug" configuration, the -cleanBuild option may clean the Release and build the Debug with

---

Quote:
-cleanBuild my_project/Debug

---

I have several configuration in my project and encounter this. I guess it will only clean the current active configuration. You probably see it on the console if trying to alter the configuration from Debug to Release with the same command line.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Apr 22 00:11:01 MST 2014
The parameter to the cleanBuild option is defined as:
{project_name_reg_ex{/config_reg_ex} | all}

where:
[list]
  [*]project_name_reg_ex is a regular expression that matches the projects you wish to build. ".*" is a regular expression that matches every project name
  [*]config_reg_ex is a regular expression for the build configurations. If you wanted to build both Debug and Release, you would use "(Debug|Release)"
[/list]

So, your command line is trying to build the "config1" buildconfiguration of the project "my_project". Did you really mean that? Or did you mean "my_project/Release"?