Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Qt Embedded Development on Mac OS X?
Forum Updated to NodeBB v4.3 + New Features

Qt Embedded Development on Mac OS X?

Scheduled Pinned Locked Moved Mobile and Embedded
4 Posts 3 Posters 4.6k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    SyntaxError
    wrote on 24 Jul 2011, 06:30 last edited by
    #1

    I spent a great deal of time compiling the CodeSourcery g++ toolchain to run natively on Mac OS X. This toolchain targets the ARM architecture.

    Now I would like to cross compile Qt/Embedded with the toolchain. The idea is to develop for embedded Linux but not use the not-so-nice Linux desktop environments.

    I am getting tons of errors. It looks like I have to hack the configure script together with the mkspecs. Does anyone want to help me do this? I can make the toolchain available to public.

    Here is the toolchain:

    Indigo:bin r2d2$ ./arm-none-linux-gnueabi-g++ -v
    Using built-in specs.
    Target: arm-none-linux-gnueabi
    Configured with: /Volumes/arm-linux-scratch/src/gcc-4.4/configure --build=x86_64-apple-darwin --host=x86_64-apple-darwin --target=arm-none-linux-gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libstdcxx-pch --enable-extra-sgxxlite-multilibs --with-arch=armv5te --with-gnu-as --with-gnu-ld --with-specs='%{funwind-tables|fno-unwind-tables|mabi=|ffreestanding|nostdlib:;:-funwind-tables} %{O2:%{!fno-remove-local-statics: -fremove-local-statics}} %{O:%{O|O0|O1|O2|Os:;:%{!fno-remove-local-statics: -fremove-local-statics}}}' --enable-languages=c,c++ --enable-shared --disable-lto --enable-symvers=gnu --enable-__cxa_atexit --with-pkgversion='ARMx 2009q3-67' --disable-nls --prefix=/Volumes/arm-x --with-sysroot=/Volumes/arm-x/arm-none-linux-gnueabi/libc --with-build-sysroot=/Volumes/arm-linux-scratch/install/arm-none-linux-gnueabi/libc --with-gmp=/Volumes/arm-linux-scratch/obj/host-libs-2009q3/usr --with-mpfr=/Volumes/arm-linux-scratch/obj/host-libs-2009q3/usr --with-ppl=/Volumes/arm-linux-scratch/obj/host-libs-2009q3/usr --with-host-libstdcxx=-Wl,-lstdc++-static,-lm --with-cloog=/Volumes/arm-linux-scratch/obj/host-libs-2009q3/usr --disable-libgomp --enable-poison-system-directories --with-build-time-tools=/Volumes/arm-linux-scratch/install/arm-none-linux-gnueabi/bin --with-build-time-tools=/Volumes/arm-linux-scratch/install/arm-none-linux-gnueabi/bin
    Thread model: posix
    gcc version 4.4.1 (ARMx 2009q3-67)

    1 Reply Last reply
    0
    • L Offline
      L Offline
      Luc4
      wrote on 24 Jul 2011, 09:25 last edited by
      #2

      Sorry, I'm not quite understanding. You recompiled the Codesourcery toolchain and want to cross-compile for arm on you mac os. But, did you write the spec file? What does the configure say?

      1 Reply Last reply
      0
      • E Offline
        E Offline
        everlook
        wrote on 30 Jul 2011, 04:06 last edited by
        #3

        If you are going to develop for an embedded linux target you need a lot more then just Qt cross compiled. You can use something like Open Embedded, PTxdist or LTIB to build your root file system which would handle building Qt. Most of these tools allow you to select different toolchains.

        As for the using the Mac - I can appreciate the desire to use the Mac since I am a Mac user myself but as you have seen that will prove difficult to manage. I suggest using VMware or Virtual Box and installing one of those "not so nice linux desktops" for embedded development.

        1 Reply Last reply
        0
        • L Offline
          L Offline
          Luc4
          wrote on 30 Jul 2011, 10:11 last edited by
          #4

          If the root filesystem is already given, why would he need Open Embedded or anything similar? If the root filesystem is already given, along with the correct toolchain, compiling Qt should be sufficient.

          1 Reply Last reply
          0

          1/4

          24 Jul 2011, 06:30

          • Login

          • Login or register to search.
          1 out of 4
          • First post
            1/4
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups
          • Search
          • Get Qt Extensions
          • Unsolved