Thanks!
 
We're currently creating a patch release (CE 2.00.01) to address a few
other minor issues reported, and will integrate this feedback as we put
that together.  There will be some updates to the example build
structure, mainly to support building for a limited set of
devices/platforms rather than all(!), so these comments are very timely.
 
I really do appreciate this kind of feedback - and am glad to see this
list provides the secondary goal of 'blowing off steam'.  ;)
 
Chris


________________________________

        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Avishai Hendel
        Sent: Sunday, December 02, 2007 8:24 AM
        To: davinci-linux-open-source@linux.davincidsp.com
        Subject: CE 2_00 examples build: blowing off steam
        
        

        Hi all (and especially the guys in TI),

        following are some problems I came across while trying to
'simply' build

        the examples directory distributed with Codec Engine 2_00,
following 

        instructions in examples/build_instructions.html. All these
problems

        can be easily overcome by some hacking, but I think it is time
that this

        will work 'out of the box', without needing to grep makefiles.

         

        + make clean

                    Does not remove all generated files and directories.
Specifically, .mak, 

                    .dep and the 'package' subdirectory. 

         

        + quote: "Change directory to ti/sdo/ce/examples/servers and
type gmake clean"

                    Alright, but here is the output:

                                make -C video_copy clean

                                make[1]: Entering directory
`workdir/CE_2_00_examples/ti/sdo/ce/examples/servers/video_copy'

                                make -C evmDM6446 clean

                                make[2]: Entering directory
`workdir/CE_2_00_examples/ti/sdo/ce/examples/servers/video_copy/evmDM644
6'

                                rm -rf video_copy.x64P
ti_sdo_ce_examples_servers_video_copy_evmDM6446.tar *.obj package
package.* video_copy

                                make[2]: Leaving directory
`workdir/CE_2_00_examples/ti/sdo/ce/examples/servers/video_copy/evmDM644
6'

                                make[1]: Leaving directory
`workdir/CE_2_00_examples/ti/sdo/ce/examples/servers/video_copy'

                                make -C all_codecs clean

                                make[1]: Entering directory
`workdir/CE_2_00_examples/ti/sdo/ce/examples/servers/all_codecs'

                                make[1]: *** No rule to make target
`clean'.  Stop.

                                make[1]: Leaving directory
`workdir/CE_2_00_examples/ti/sdo/ce/examples/servers/all_codecs'

                                make: *** [clean] Error 2

         

        + the 'build_instructions' file directs the users to edit
user.bld and 

        xdcpaths.mak files, in addition to paths in GPP applications. It
fails to 

        mention the servers/video_copy/evmDM6446/makefile, which also
needs to be 

        edited (a bug?), and set the CGTOOLS directory again.

         

        + the 'build_instructions' file also fails to mention that a
compilation of

        the 'extensions' subdirectory is required.

         

        + more troubles creating video_copy and all_codecs DSP servers:

                    $ make

                     ...

                                            js:
"/opt/dvevm/xdc_3_00_02/packages/xdc/cfg/Main.xs", line 170: exception
from uncaught JavaScript throw: Error: incompatible use of package
'ti.rtdx': imported ti.rtdx [2,0,0,1,1194024051755], ti.bios.utils was
built with ti.rtdx []

                                            Adding the following line to
your configuration script:

        
environment['xdc.cfg.check.fatal'] = 'false';

        converts this incompatibility error into a warning. Please,
check the documentation for the package xdc.cfg for more information.

                     ...

         

                     (and where exactly is 'the documentation for the
package xdc.cfg' ?)

         

         

        All of the above was done with latest packages available from
DVEVM update site.

        Hope someone will take the time and fix these annoyances in
future releases (or correct

        Me if I had done something wrong along the way).

         

_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to