Problems building CCS4 projects from command line

I think that command just does a clean on the project. Is that what you want to do? If you want to actually build it, remove the '-ccs.clean' option at the end.

Thanks

ki

I tried removing the clean as well but still doesnt work

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

CCS headless build starting... [Thu Dec 03 16:45:46 GMT 2009]

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================

Pre processing...

================================================================================

Building...

--------------------------------------------------------------------------------

**** Build of configuration Release for project l_C64 ****

Nothing to build for project l_C64

================================================================================

CCS headless build complete!

All the source files in the project have been added as a link

The command you are using looks fine. Any chance you can send me your project? You can attach to this thread or contact me via private conversation for my contact.

Thanks

ki

Pavan,

I tested here with a project full of linked files and could build fine. I added the option (-ccs.autoOpen) to make sure the project was open before any build attempts. I built the project after performing a clean.

My command lines were:

C:\Program Files\Texas Instruments\ccsv4\eclipse>.\jre\bin\java.exe -jar startup.jar -data "C:\Documents and Settings\a0356111\My Documents\workspace" -application com.ti.ccstudio.apps.projectBuild -ccs.projects linked_test -ccs.autoOpen -ccs.clean

C:\Program Files\Texas Instruments\ccsv4\eclipse>.\jre\bin\java.exe -jar startup.jar -data "C:\Documents and Settings\a0356111\My Documents\workspace" -application com.ti.ccstudio.apps.projectBuild -ccs.projects linked_test -ccs.autoOpen -ccs.configuration Debug

Hope this helps,

Rafael

Hi,

  My project has a linked in folder ... and that folder has various files. 

If I import the project using the GUI and then build it from command line it works fine ...

But if I import it from the command line it does not build .. I think it doesnt find the source files....

I have a trial project if you wish to try out ... how do I send it to you .. I dont wish to use the public thread.

Regards,

Pavan

Hi Pavan,

Go to my profile: http://e2e.ti.com/user/Profile.aspx?UserID=2210

Under my picture, there is an option to "Start a Conversation" (or something similar). This will start a private conversation and I will provide more details there.

Thanks

ki

Pavan,

so does this mean you have an existing CCS v4 project, created using the gui, and now you want to import (move) it via command line somewhere else

Pavan Bhave said:

All the source files in the project have been added as a link

referring to:http://tiexpressdsp.com/index.php/Projects_-_Command_Line_Build/Create

the comment you gave seems to indicate you are referencing the original project.

I have seen there is a command

-ccs.copyIntoWorkspace

which might be helpful as it should copy over the sources (and not leave them as links), Did you try this?

I do not wish to copy the files to the workspace ... as I want to have a separate directory structure for all the files I have created. I have emailed  a sample project which is similar to what I have.

I can build the project happily using the GUI.

 Now I want to a script that builds my project and therefore need to build my project from command line.

Looking forward for your help,

regards,

Pavan

in macros.ini there is the definition of where the sources are located

            EXT_ROOT__l_base = ../
            DSP_MODULE = ../../../../

and your .project looks like the following:

...
<linkedResources>
        <link>
            <name>source</name>
            <type>2</type>
            <locationURI>DSP_MODULE/source</locationURI>
        </link>
    </linkedResources>
....

CCS should be able to resolve the macros.ini, in order to find the sources

but I don't see a way to specify the macros.ini on the command line - so I'm not 100% sure if the macros.ini will be used by the command line tools, i.e. will be automatically imported as well. But I believe it should be possible to reference other files/directories even from the command line build

maybe the macro.ini setup is the reason why the command line version as you suspect does not find the sources?

I tried to get the test project copied over but it is not copying the sources either, and I tested several combinations of the macro.ini files so far.

it seems that any folder is copied only if it is a subfolder of the project dir.

can you check the macros.ini are working at all on your side in other configurations? (maybe try a folder which is just one level away from the project dir, for simplicity)

what about putting the arguments in a separate file, using -ccs.args <file>, does this make a difference ?

Yes I think you are right.

The Macros.ini file defines a vriable which is the relative path to the project files from the .cdtbuilt file location.

The GUI seems to resolve the paths OK…. Issue the build command from the workspace?

Regards,

Pavan Bhave

if I add 

pathvariable.DSP_MODULE =  fullpath

and

pathvariable.EXT_ROOT__l_base = full path

 to the file

.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclipse.core.resources.prefs 

It builds the project.

I think the command line tool is not reading the macros.ini file