[aspectc-user] Compile after weaving

[Olaf Spinczyk]

Hello Yan,

I am sorry that I have to say it, but ac++ *does not support VC 6.0*. 
The reason is that VC 6.0 is unable to compile the standard complient 
code that is generated by ac++. It only works in very simple cases. As 
VC 6.0 is rather old and has a shrinking user community, we decided a 
few year ago that we are not going to develop any workarounds for the 
shortcomings of this compiler.

Best regards,

Olaf


Yan Mao wrote:
> -------- Original-Nachricht --------
> Datum: Fri, 14 Jul 2006 18:19:22 +0200
> Von: Olaf Spinczyk <Olaf.Spinczyk at informatik.uni-erlangen.de>
> An: Yan Mao <maoyan at gmx.net>
> Betreff: Re: [aspectc-user] Compile after weaving
>> If you are asking for the easiest way, then I can only recommend to 
>> download the AspectC++ Add-In for Visual Studio .NET from 
>> www.pure-systems.com. It is commercial, but a trial version is available.
>>
>> The problem is to get the right parser configuration file for ac++ (e.g. 
>> puma.config). This is not trivial. In the case of g++, the ag++ command 
>> generates the parser configuration file for you. In the case of VC++, 
>> the AspectC++ Add-In for Visual Studion also comes with a valid parser 
>> configuration file. Writing it manually means that you have to find out 
>> and enter all built-in include paths and predefined macros of your 
>> compiler. Therefore, have a look at the Add-In.
>>
>> If you want to dig deeper without the Add-In, I would recommend to use 
>> the single translation unit mode, where includes are automatically 
>> expanded by the weaver. The generated #line directives make sure that 
>> line numbers in error messages are correct (mostly).
>>
>> => ac++ -p Trace -I Trace -c Trace/main.cpp -o Trace/Debug/main.cpp
>>     (also -I Trace/inc?)
>>
>> Finally, compile all files in Trace/Debug with VC++.
>>
>> I hope this helps,
>>
>> Olaf
> 
> Hello Olaf,
> 
> I really want to dig deeper without the Add-In, since my current project uses VC++ 6.0, but it seems, it would be no so easy.
> I have tried the single translateion unit mode, as you suggested, but it didnt work, the same errors came up.
> So I am going to take a look at Visual Studio .NET, to think, if i can find a compromise for my VC 6.0 Project, or change to use VS.NET.
> 
> thanks for quick answer,
> 
> Yan
>