Compiling ACE for vxworks 5.5.
MoveLik...@gmail.com
my company is soon starting a "extreme makeover" project of the
current code. Current software uses VxWorks 5.5 with all the code
written in C. In the new software it will be used c++ and also VxWorks
5.5. The goal in the new software is to write code and compile it for
both windows and vxworks, thuse making it possible to do some testing
at the NT developer machine. Im on a "quest" for checking if ACE can
be the OS abstraction layer we are looking for.
I downloaded the the newest ACE from the download site, and have been
following the ACE-INSTALL.html document. I had no problems compiling
ACE for windows, but run into problems when trying to compile for
vxworks 5.5. I tried to search the group and found some configs other
people had used but im still getting the same error. Should vxworks
5.5 compile "out of the box" by following the guidelines? Hopefully im
making some easy beginner error.
My config.h looks like this:
#if defined (_MSC_VER) || (__BORLANDC__)
#include "ace/config-win32.h"
#undef ACE_HAS_EXCEPTIONS
#else
#include "ace/config-vxworks5.x.h"
#endif
My platform_macros.GNU:
static_libs=1
debug=1
inline=0
fl_reactor=0
optimize=0
WIND_BASE = c:\Tornado2.2
WIND_HOST_TYPE = x86-win32
CPU = PENTIUM
include $(ACE_ROOT)/include/makeinclude/platform_vxworks5.5.x.GNU
I run make from cygwin shell:
$ make static_libs=1
This is the output:
'-dumpversion' is not recognized as an internal or external command,
operable program or batch file.
make[1]: Entering directory `C:\ACE_wrappers\ace'
GNUmakefile: /ace/ace/GNUmakefile.ACE MAKEFLAGS=-w -- static_libs=1
ccpentium -mcpu=pentium -march=pentium -ansi -Ic:\Tornado2.2\target/
h -DCPU=PENTIUM -DTOOL_FAMILY=gnu -DTOOL=gnu -ftemplate-depth-50
-fno-exceptions
-DACE_VXWORKS=0x551 -Ic:\ACE_wrappers -DACE_HAS_EXCEPTIONS -I.. -
DACE_AS_STATIC_LIBS -c Local_Name_Space. Local_Name_Space.cpp
ccpentium: Local_Name_Space.: No such file or directory
In file included from c:/ACE_wrappers/ace/OS_NS_stropts.h:168,
from c:/ACE_wrappers/ace/OS_NS_sys_socket.h:30,
from c:/ACE_wrappers/ace/ACE.inl:8,
from c:/ACE_wrappers/ace/ACE.h:820,
from c:/ACE_wrappers/ace/Malloc_T.cpp:16,
from c:/ACE_wrappers/ace/Malloc_T.h:923,
from c:/ACE_wrappers/ace/Local_Name_Space.h:20,
from Local_Name_Space.cpp:1:
c:/ACE_wrappers/ace/OS_NS_stropts.inl: In function `int ACE_OS::putmsg
(int, const strbuf *, const strbuf *, int)':
c:/ACE_wrappers/ace/OS_NS_stropts.inl:171: exception handling
disabled, use -fexceptions to enable
c:/ACE_wrappers/ace/OS_NS_stropts.inl:171: confused by earlier errors,
bailing out
make[1]: *** [Local_Name_Space.] Error 0x1
make[1]: Leaving directory `C:\ACE_wrappers\ace'
Douglas C. Schmidt
>my company is soon starting a "extreme makeover" project of the
>current code. Current software uses VxWorks 5.5 with all the code
>written in C. In the new software it will be used c++ and also VxWorks
>5.5. The goal in the new software is to write code and compile it for
>both windows and vxworks, thuse making it possible to do some testing
>at the NT developer machine. Im on a "quest" for checking if ACE can
>be the OS abstraction layer we are looking for.
>
>I downloaded the the newest ACE from the download site,
It's not clear what you mean by "newest ACE". To ensure that we have
proper version/platform/compiler information, please make sure you
fill out the appropriate problem report form (PRF), which is in
$ACE_ROOT/PROBLEM-REPORT-FORM
$TAO_ROOT/PROBLEM-REPORT-FORM
or in
$ACE_ROOT/BUG-REPORT-FORM
$TAO_ROOT/BUG-REPORT-FORM
in older versions of ACE+TAO. Make sure to include this information
when asking any questions about ACE+TAO since otherwise we have to
"guess" what version/platform/compiler/options you've using, which is
very error-prone and slows down our responsiveness.
>and have been
>following the ACE-INSTALL.html document. I had no problems compiling
>ACE for windows, but run into problems when trying to compile for
>vxworks 5.5. I tried to search the group and found some configs other
>people had used but im still getting the same error. Should vxworks
>5.5 compile "out of the box" by following the guidelines?
Good question. I don't think we are doing much with VxWorks 5.5 these
days since our recent VxWorks users have moved to VxWorks 6.x.
Johnny, can you please add more to this discussion based on your
experience?
Thanks,
Doug
--
Dr. Douglas C. Schmidt Professor and Associate Chair
Electrical Engineering and Computer Science TEL: (615) 343-8197
Vanderbilt University WEB: www.dre.vanderbilt.edu/~schmidt
Nashville, TN 37203 NET: d.sc...@vanderbilt.edu
MoveLik...@gmail.com
> It's not clear what you mean by "newest ACE". To ensure that we have
> proper version/platform/compiler information, please make sure you
> fill out the appropriate problem report form (PRF), which is in
>
> $ACE_ROOT/PROBLEM-REPORT-FORM
> $TAO_ROOT/PROBLEM-REPORT-FORM
>
> or in
>
> $ACE_ROOT/BUG-REPORT-FORM
> $TAO_ROOT/BUG-REPORT-FORM
>
im sorry didnt gave information the proper way, here I try again :)
ACE VERSION: 5.6.5
HOST MACHINE and OPERATING SYSTEM
Pentium, Windows xp
TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
COMPILER NAME AND VERSION (AND PATCHLEVEL):
Pentium, VxWorks 5.5, Tornado 2.2
THE $ACE_ROOT/ace/config.h FILE [if you use a link to a platform-
specific file, simply state which one]:
#if defined (_MSC_VER) || (__BORLANDC__)
#include "ace/config-win32.h"
#undef ACE_HAS_EXCEPTIONS
#else
#include "ace/config-vxworks5.x.h"
#endif
THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE [if you
use a link to a platform-specific file, simply state which one
(unless this isn't used in this case, e.g., with Microsoft Visual
C++)]:
static_libs=1
debug=0
inline=0
fl_reactor=0
optimize=0
WIND_BASE = c:\Tornado2.2
WIND_HOST_TYPE = x86-win32
CPU = PENTIUM
include $(ACE_ROOT)/include/makeinclude/platform_vxworks5.5.x.GNU
CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/
default.features
(used by MPC when you generate your own makefiles):
didn't touch this.
Problem:
Doesent compile for VxWorks.
This is the output:
Im pretty clueless about makefilesystem and unix "stuff", so it
wouldnt surprise me if i have done some stupid mistake when following
the guidelines. Would be really helpfull if i could get some pointers
to get it working :).
Sincerely,
Rune
Johnny Willemsen
> >and have been
> >following the ACE-INSTALL.html document. I had no problems compiling
> >ACE for windows, but run into problems when trying to compile for
> >vxworks 5.5. I tried to search the group and found some configs other
> >people had used but im still getting the same error. Should vxworks
> >5.5 compile "out of the box" by following the guidelines?
>
> Good question. I don't think we are doing much with VxWorks 5.5 these
> days since our recent VxWorks users have moved to VxWorks 6.x.
> Johnny, can you please add more to this discussion based on your
> experience?
VxWorks 5.5.x is currently supported, but only through our commercial
support services. It is a very expensive OS to maintain and it has its
special setup. We have made special setup instructions for our customers and
we support windows and solaris host systems. We do have a daily build setup,
see http://scoreboard.theaceorb.nl. We do maintain this port currently until
end of August, after that we run out of sponsoring again. If you are
interested in this port, contact me directly about the support options. Also
let your WindRiver contacts know you are interested in ACE/TAO.
Regards,
Johnny Willemsen
Remedy IT
Postbus 101
2650 AC Berkel en Rodenrijs
The Netherlands
www.theaceorb.nl / www.remedy.nl
*** Integrated compile and test statistics see
http://scoreboard.theaceorb.nl ***
*** Commercial service and support for ACE/TAO/CIAO ***
*** Get your free TAO Programmers Guide copy from
http://www.theaceorb.nl ***