|
Boost-Build : |
From: Andre Hentz (ahentz_at_[hidden])
Date: 2004-09-24 02:31:14
Vladimir Prus wrote:
> Hi Andre,
>
>
>> I'm trying to get my projects to work with the new matlab and I'm
>>failing. I'd appreciate some help here.
>>
>> The matlab compiler basically does:
>>
>> .m -> _main.c, _mcc_component_data.c, .ctf
>>
>>The idea is to send the .c files into the appropriate compiler and
>>install the .ctf file using a stage rule.
>>
>>I've tried a few different things and decided that I'd have to write my
>>own genenator. Is that the way to go? If so, can someone give a hint on
>>how to write the run rule? I'm a bit confused.
>
>
> First of all, some questions.
>
> 1. Are the name of the output files hardcoded? If I use "a.m" do I get
> "_main.c" or "a_main.c"?
>
a.m create a_main.c. I have no control over that.
> 2. How do you plan the "m" files to be used? Could you give a specific example
> of Jamfile code that you want to work?
>
> I've tried this (m.jam):
>
> import type ;
> type.register M : m ;
> type.register CTF : ctf ;
>
> import generators ;
>
> generators.register-standard m.mex : M : C(%_main) C(%_component_data) CTF ;
>
> actions mex
> {
> touch $(<) ;
> }
>
>
> together with:
>
> exe a : a.m ;
> stage x : a ;
>
> and it almost works, except that the CTF file is not staged. Is that's the
> problem you want to fix?
>
Yes. That's one of the problems.
The other proble is that the C files were being compiled and linked
before the "touch", which was wierd. I'll try again and let you know.
Thanks in advance
Andre Hentz
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk