This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
I have a working project which builds "Debug" and "Release" ELF dlls.
I need to build different variants of the same dll which differ only by a couple of settings each, such as preprocessor definitions and linker output name (--define, -o).
The most obvious thing to do is to create a custom build configuration copying it from the "Release" configuration, which I have done.
However, when I build the new customised configuration I get the following error:
**** Build of configuration Release_3B for project EqAAX_Mono_Mono_TI ****
C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all
gmake: *** No rule to make target `C:\svn\PlugIn_PT\AAX_SDK_1p0p4\SonnoxPlugIns\AAX_SonnoxEQ\TI\EqAAX_Mono_Mono_TI/../../WinBuild/Release_3B/OxfordEQ.aaxplugin/Contents/Resources/OxfordEQ_3Band_Mono_Mono_TI.dll', needed by `all'.
gmake: Target `all' not remade because of errors.
Build complete for project EqAAX_Mono_Mono_TI
I need support on how to get this working please...
Hi,
Which specific version of CCSv4 are you using?
There have been a couple of other instances where similar issues have been reported. Please see this threads:
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/86752.aspx
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/115694.aspx
In one case updating to CCS5 resolved the problem. I am not sure if that is a feasible option for you at this point, but at a minimum I would suggest making sure you are up to at least 4.2.4 or 4.2.5. You should be able to update to this either from within CCS menu Help->Software Updates->Find and Install or downloading the full installer and reinstalling from here.
Hi ArtiG,
it looks like it is the same issue.
I was using CCS4.2.4 and have just upgraded to 4.2.5, however it does not make a difference and the same error still pops up.
I am not allowed to go CS5 yet as it has not been fully tested by the company I am building the dlls for.
So, my only chance would be to follow the second thread you posted. Can you exactly explain what "After changing the device configuration" means?
cheers
Marcello Gagliardi said:So, my only chance would be to follow the second thread you posted. Can you exactly explain what "After changing the device configuration" means?
Unfortunately, I'm really not sure what that user meant by that statement and how exactly the issue was resolved. You are welcome to post an update on that thread and try to get more details from that user directly.
The only other option is if you wish to share your project so we can recreate and analyze the issue and see if our developers can find a useable workaround. There is no guarantee though that there may be a suitable workaround but it may be worth a try before you resort to going down the path of creating a new configuration from scratch.