RE: Compiling Targets and Codecs
Hi Steven, I'm not sure why you are asking me. I don't work for TI I'm just a member of the davinci mailing list and I try to help out when I know the answer. In this case I don't really know the answer other than you doing a search of your file system. If you have the default install of the dvevm cd mine is located at /home/harsha/dvevm/cgtools/bin/cl6x In the future I would post your question to davinci-linux-open-source@linux.davincidsp.com Also you need to sign up for the mailing list here: http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source Josh -Original Message- From: steven.zhang [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 26, 2008 3:59 AM To: [EMAIL PROTECTED] Subject: Compiling Targets and Codecs Hi, joshh~ I am now trying to compile the TI codec server, However, I can not find cl6x compiler in my system(FC8). Could you please tell me how to get the cl6x compiler? thanks so much. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Compiling Targets and Codecs
Please review this thread and see if it answers your question. http://osdir.com/ml/linux.davinci/2006-09/msg00095.html In short, your codec package can just have a 64P library, but you may have to adjust its getlibs() fxn as described at the link above. Chris From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joshua Hintze Sent: Thursday, February 07, 2008 8:58 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: Compiling Targets and Codecs Hello, I am running with the DM6446 processor and something that I have not yet figured out is the compiling targets when working with the codec engine. What I mean is if I want to have the codec running on the DSP and the executable running on the ARM do I need to produce two different libraries for the codec? It seems the app likes to link with .a470MV. However if I turn off the MVArm9 build target in user.bld this file no longer gets generated. My questions are, can I get the linux side app to link with .a64P? The reason why I only want to generate the .a64P is because I have a lot of cl6x (DSP) only code in my codec, that takes advantage of DSP optimizations and the arm compiler chokes on that when compiling the codec. I noticed in the linux app makefile there is an XDCTARGET that is set to XDCTARGET = gnu.targets.MVArm9. I tried gnu.targets.C64P with no luck. Thanks, Josh ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Compiling Targets and Codecs
Thanks Chris this worked great. I have another quick question. How can I change the cl6x compiler switches that are defaulted in the Codec Engine when using package.bld. For example I want to add a couple like: -pm -op2 and change -o2 to -o3. Thanks, Josh From: Ring, Chris [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 12:20 PM To: Joshua Hintze; davinci-linux-open-source@linux.davincidsp.com Subject: RE: Compiling Targets and Codecs Please review this thread and see if it answers your question. http://osdir.com/ml/linux.davinci/2006-09/msg00095.html In short, your codec package can just have a 64P library, but you may have to adjust its getlibs() fxn as described at the link above. Chris _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joshua Hintze Sent: Thursday, February 07, 2008 8:58 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: Compiling Targets and Codecs Hello, I am running with the DM6446 processor and something that I have not yet figured out is the compiling targets when working with the codec engine. What I mean is if I want to have the codec running on the DSP and the executable running on the ARM do I need to produce two different libraries for the codec? It seems the app likes to link with .a470MV. However if I turn off the MVArm9 build target in user.bld this file no longer gets generated. My questions are, can I get the linux side app to link with .a64P? The reason why I only want to generate the .a64P is because I have a lot of cl6x (DSP) only code in my codec, that takes advantage of DSP optimizations and the arm compiler chokes on that when compiling the codec. I noticed in the linux app makefile there is an XDCTARGET that is set to XDCTARGET = gnu.targets.MVArm9. I tried gnu.targets.C64P with no luck. Thanks, Josh ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
