Michael Marcin wrote:
> Hello,
>
> Our development toolchain was changed because of
external conditions from
> a reasonably fast CodeWarrior based build process to a
windows batch file
> + perl + make voodoo process which is horribly slow (a
trivial change to 1
> cpp file + compile takes ~10 minutes).
>
> I'm trying to quickly implement BBv2 support for armcc
and armlink for
> RVCT 2.2 sp1 (as well as for the OS and standard
library our platform uses
> but first thing is first).
>
> I tried hacking a few of the files in the v2/tools
directory and borland
> seemed to be the simplest so I started from it.
>
> I've attached what I've been able to come up with so
far.
>
> Trying to compile a test project gives:
>
> C:Codengi_bbv2audioexprojectsbbv2>bjam
toolset=rvct
> C:/Code/ngi_bbv2/boost_build/v2/kernelmodules.jam:66:
in modules.call-in
> rule rvct.link unknown in module rvct.
Sure enough. You have this:
generators.register-linker rvct.link : OBJ
SEARCHED_LIB STATIC_LIB IMPORT_LIB : EXE :
<toolset>rvct ;
which basically say: "to produce EXE", use
action/rule pair called "rvct.link".
You can read more about action/rule pairs at the bottom of
generators.register-linker rvct.link : OBJ SEARCHED_LIB
STATIC_LIB IMPORT_LIB : EXE : <toolset>rvct ;
However, you don't have any action name 'link' in your
rvct.jam. While borland.jam has
something like:
actions link
{
$(.set-path)$(.root:W)$(.old-path)
"$(CONFIG_COMMAND)" -v -q $(OPTIONS)
-L"$(LIBRARY_PATH:W)"
-L"$(STDLIBPATH:W)" -e"$(<[1]:W)"
" ($(<[1]:W).rsp:E=$(nl)"$(>)"
$(nl)$(LIBRARIES)
$(nl)"$(LIBRARY_OPTION)$(FINDLIBS_ST:S=.lib)"
$(nl)"$(LIBRARY_OPTION)$(FINDLIBS_SA:S=.lib)")&quo
t;
}
you don't have anything like that. Basically, you did not
say what command should be used
for linking. I presume you've just forgot to add that.
- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
a>
|