Tornado 2.0 adding componets

[Greg Willden]

> Does anyone know how I can tell Tornado where it should look
> for my object files so that can be added using the project
> facility and will get linked with the main project?

Go to the Builds tab of the workspace window and right click on the specific
build that you are using and select Properties. Go to the Macros tab of the
pop-up window and under PRJ_LIBS add the path and filename of any archive
files that you want to link to. If you want to link in .o files you go to
the linker tab and specify the .o files.

>
>
> Second problem:
> During Tornado 1.0 time, we built and linked the modules using makefiles,
> this created one .O file for each module, which we then linked with the
> main project. Now I don't know the correct way to create these modules.
> If I create them by creating a "downloadable application module"with
> Tornado 2.0, I either have multiple .O files (one for each .C file) or
> an .a archive or an .out file, depending on the link rule. Neither of
> these seem to be the correct one. What can I do?
>

You want to create a downloadable application module that links to a .out
file. This .out file consists of all the .o's generated in compilation, the
libs specified in the PRJ_LIBS and any other .o's that you specify in the
linker section.

Hope this helps

[jo...@borksoft.xs4all.nl]

Marcus Overhagen <Usenet2...@overhagen.de> wrote:
: To get started, I created a new file in \target\config\coms\vxWorks
: which I called 00toolkit.cdf. This file defines a new FOLDER_TOOLKIT
: where I want to manage my components.
: I also added this FOLDER_TOOLKIT to the FOLDER_ROOT folder in file
: 00vxWorks.cdf

You don't have to change the 00vxWorks.cdf file. If you define the item
_CHILDREN in your cdf file and give this the value FOLDER_ROOT it will be
added to the root folder, and you don't get problems when WindRiver
releases a new version of the 00vxWorks.cdf.

: It looks like it does not find the neccessary object files, regardless
: where I place them.
: I already tried:
: \tornado\target\
: \tornado\target\lib\objCPU32gnuvx
: \tornado\target\config
: \tornado\target\config\MY_BSP
: \tornado\target\project\MY_PROJECT

: All object files of components belonging to Tornado seem to be archived
: in the file \tornado\target\lib\libCPU32gnuvx.a

Add you components to a new archive that is company specific, for example
libCompanyCPU32.a. Then add this library to the LIBS macro in the build
specs.
If you want to use this library for all your projects add this library to
the LIB_EXTRA macro in the BSP Makefile.
It is possible that all other items in your configuration now become
unavailable. To avoid this you have to make some changes to the file
prj_vxworks.tcl. See
http://www.xs4all.nl/~borkhuis/vxworks/vxw_pt2.html#2.6.2 for more info on
this.

: During Tornado 1.0 time, we built and linked the modules using makefiles,

: this created one .O file for each module, which we then linked with the
: main project. Now I don't know the correct way to create these modules.
: If I create them by creating a "downloadable application module"with
: Tornado 2.0, I either have multiple .O files (one for each .C file) or
: an .a archive or an .out file, depending on the link rule. Neither of
: these seem to be the correct one. What can I do?

You can select the build-rule objects, this will only generate the objects
per C-file.

Groeten,
Johan

--
o o o o o o o . . . ___________________________________
o _____ || Johan Borkhuis |
.][__n_n_|DD[ ====_____ | jo...@borksoft.xs4all.nl |
>(________|__|_[_________]_|________________________________|
_/oo OOOOO oo` ooo ooo 'o!o!o o!o!o`
=== VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===