Disko Forum logo Login  |  Register  |  Lost Password
<< Start < Prev 1 2 3 Next > End >>
Cross Compiler DISKO-1.6.0 to DM6446

Bermuda
Posts: 21
graphgraph

Cross Compiler DISKO-1.6.0 to DM6446 4 Years, 4 Months ago  
Dear all:

I have tried to cross compiler for several days...but still not work.

Code:

root@BERMUDA-MMN:~# env | grep arm PATH=/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/:/opt/tool/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LD=arm_v5t_le-ld CXX=arm_v5t_le-g++ RANLIB=arm_v5t_le-ranlib CC=arm_v5t_le-gcc
Code:

scons prefix=/home/bermuda/disko-1.6.0/build/ destdir=/opt/mv_pro_5.0/montavista/pro/devkit/arm/ debug=yes messages=yes cross=yes profile=yes use_dl=yes static_lib=yes
And then I see something wrong about these...
  • cc1plus: warning: include location "/usr/include/sigc++-2.0" is unsafe for cross-compilation
  • cc1plus: warning: include location "/usr/include/libxml2" is unsafe for cross-compilation
  • cc1plus: warning: include location "/usr/include/libpng12" is unsafe for cross-compilation
  • cc1plus: warning: include location "/usr/include/freetype2" is unsafe for cross-compilation
  • cc1plus: warning: include location "/usr/include/gstreamer-0.10" is unsafe for cross-compilation
  • cc1plus: warning: include location "/usr/include/glib-2.0" is unsafe for cross-compilation
  • cc1plus: warning: include location "/usr/include/alsa" is unsafe for cross-compilation
  • I guess that is because I have not cross compiler all these libraries. is there anyone can give me some suggestions about this...? also I have try to cross compiler sigc++-2.0 but I dont know how to let this library to be referenced by disko.
     
      The administrator has disabled public write access.
    Cross Compiler DISKO-1.6.0 to DM6446

    Matthias
    Posts: 64
    graphgraph

    Gender: Male Disko Location: Berlin, Germany Birthdate: 1979-04-25
    Re:Cross Compiler DISKO-1.6.0 to DM6446 4 Years, 4 Months ago  
    Hello Bermuda,

    as I can see, you are using the Montavista 5.0 toolchain. I never tried it, so I don't know what they are using as their build system. I only read, that recently (in MVL6) it is based on OpenEmbedded.

    However, you are definitely right, that you have to build all dependencies of disko for your target platform. You can minimize the set of libraries, by disabling the media backend and/or ALSA if not needed.

    If you decide to use OpenEmbedded, you can have a look at our HowTo for the BeagleBoard (http://www.diskohq.com/developers/documentation/omap/beagleboard.html). There you can download recipes to build disko.

    Hopefully this gives you a better starting point. If you have any more questions, feel free to ask.

    Best regards,
    Matthias
     
     
    Last Edit: 2010/04/06 09:57 By Matthias.
      The administrator has disabled public write access.
    Cross Compiler DISKO-1.6.0 to DM6446

    Bermuda
    Posts: 21
    graphgraph

    Re:Cross Compiler DISKO-1.6.0 to DM6446 4 Years, 4 Months ago  
    Thanks for replay so quickly... I still working...

    1.Is there some example about cross compiler those libraries??

    Also how can I check if I cross compiler it successfully??(with "file" command??)


    It's because I have tried to cross compiler libsigc++
    and after I type "make" command , I get three folders in libsigc++

    1.include
    2.lib
    3.share

    should I copy all of these to a particular path so that disko can find them??



    2.If I decide to use openembedded ,should I cross compiler all those libraries still??

    3.How can I make sure that disko can run correctly on my board(Davinci DM6446)??
    ex.hardware dependency...

    4.May I give u my msn account so I can ask u more easily (if u dont mind it)
     
      The administrator has disabled public write access.
    Cross Compiler DISKO-1.6.0 to DM6446

    Matthias
    Posts: 64
    graphgraph

    Gender: Male Disko Location: Berlin, Germany Birthdate: 1979-04-25
    Re:Cross Compiler DISKO-1.6.0 to DM6446 4 Years, 4 Months ago  
    QUOTE:
    Is there some example about cross compiler those libraries


    Well, this depends on the libraries. If you are using a build system, you probably have already scripts or Makefiles that'll build them.

    In general software that uses autoconf tools (like libsigc++ does), you can often use
    Code:

    ./configure --prefix=${STAGINGDIR} --host=arm_v5t_le
    where STAGINGDIR defines your installation directory and --host depends on your target architecture. If you now install everything into STAGINGDIR, you can set your CFLAGS and LDFLAGS accordingly. Then you should be able to compile everything, keeping in mind the dependencies between each of the libraries.
    QUOTE:
    Also how can I check if I cross compiler it successfully??(with "file" command??)
    For executables or shared libraries this works. For static libraries not, but you can check the object files.
    QUOTE:
    If I decide to use openembedded ,should I cross compiler all those libraries still??
    Yes, but this will be much easier, as they are already included in the Angstrom distribution. Then you can use our overlay from the beagleboard HowTo mentioned earlier and simply configure your machine. You can even start by using the neuros-osd2 configuration which is a DM6446 as well.
    QUOTE:
    How can I make sure that disko can run correctly on my board(Davinci DM6446)??
    We tried disko already on the Neuros OSD2 board (http://wiki.neurostechnology.com/index.php/OSD_2.0_HD), which is a DaVinci DM6446.
    QUOTE:
    May I give u my msn account so I can ask u more easily (if u dont mind it)
    I'm not using MSN, but you can contact me on ICQ (290990941) if you wan't to. Maybe we'll have an IRC channel in the future for discussions like that. Best regards, Matthias
     
      The administrator has disabled public write access.
    Cross Compiler DISKO-1.6.0 to DM6446

    Bermuda
    Posts: 21
    graphgraph

    Re:Cross Compiler DISKO-1.6.0 to DM6446 4 Years, 4 Months ago  
    Now I still working to cross compiler those libraries...

    But when I try to use openembedded, here is something error message I got:

    ==
    Traceback (most recent call last):
    File "/usr/bin/bitbake", line 143, in <module>
    main()
    File "/usr/bin/bitbake", line 123, in main
    cooker.parseConfiguration()
    File "/usr/lib/pymodules/python2.6/bb/cooker.py", line 68, in parseConfiguration
    self.parseConfigurationFile( os.path.join( "conf", "bitbake.conf" ) )
    File "/usr/lib/pymodules/python2.6/bb/cooker.py", line 404, in parseConfigurationFile
    bb.event.fire(bb.event.ConfigParsed(self.configuration.data))
    File "/usr/lib/pymodules/python2.6/bb/event.py", line 67, in fire
    if tmpHandler(event) == Handled:
    File "tmpHandler(e)", line 4, in tmpHandler
    File "<bb>", line 18, in check_sanity
    NameError: global name 'os' is not defined
    ==

    I have google this problem it's seems there are two ways to slove

    1.insertion "import os"
    2.modify conf/bitbake.conf

    but still not work@@

    by the way my OS is ubuntu 9.10


    PS. I have add ur ICQ number. Hoping I can see u soon thanks a lot and a lot...
     
      The administrator has disabled public write access.
    Cross Compiler DISKO-1.6.0 to DM6446

    Matthias
    Posts: 64
    graphgraph

    Gender: Male Disko Location: Berlin, Germany Birthdate: 1979-04-25
    Re:Cross Compiler DISKO-1.6.0 to DM6446 4 Years, 4 Months ago  
    I remember that I had trouble with the bitbake version that ships with Ubuntu.
    So I installed bitbake 1.8.18. Maybe this helps.
     
      The administrator has disabled public write access.
    << Start < Prev 1 2 3 Next > End >>
    Powered by FireBoard
    get the latest posts directly to your desktop