• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 1603 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

enet_echo example in starterware under windows

Ahmed Wefky
Intellectual 370 points

Hello everybody,

I booted a beaglebone black from a SD card carrying the enet_echo binary file from the starterware package.

Under Linux Ubuntu, I compiled and executed the enet_client application using gcc and everything worked fine.

When I tried to compile the enet_client c code under windows, I got a lot of compilation errors. Can that code be compiled under windows? If so, has anyone tried to compile it under windows?

Best regards,

  • 0
    Genius 5820 points

    Without knowing any details and without knowing what compilation errors you got, I only can guess: Using Windows you do not have a GCC, means you have to use TI's ARM compiler. So you can't reuse any GCC-binaries from your Linux installation and have to recompile everything - not only the example but also all depending libraries.

  • 0 in reply to qxc
    TI__Mastermind 44306 points

    Hi,

    qxc said:
    Using Windows you do not have a GCC, means you have to use TI's ARM compiler.

    This is obviously not true. Since quite some time we do have a GCC based compiler in CCS for all the higher-end ARM cores.

    Indeed we are missing details on the issue. I assume this is just a build or make file issue as usually Starterware does not require external headers/libs except what is in the package coming with the compiler.

    Regards,

  • 0 in reply to Frank Walzer
    Genius 5820 points
    > Since quite some time we do have a GCC based compiler in CCS for all the higher-end ARM cores.

    Hm, OK, this was new for me - I have seen CCS on Windows only once and a really long time ago...
  • 0 in reply to Frank Walzer
    Intellectual 370 points

    Hello Frank and "qxc",

    First of all, thanks for your interest and your trial to help me out.

    I finally found a solution for my problem.

    The linux_X86_64 bits_GNU_C_Compiler already has a built-in sockets library (sys/sockets.h). So when I compiled the client c code from the host apps folder in the starterware package, it worked fine under linux.

    In windows, the X86_64_bits_GNU_Compilers like (MINGW, CYGWIN,...) don't have a built in sockets library. So the most straight forward solution is to use a third party sockets library like the NDK from Texas Instruments. I rebuilt the echoc.c in the winapps directory of the NDK using Microsoft's visual studio 2010 after just changing the port number from 7 to 2000 and everything now works very good.

    Best regards,