Hi all - We're trying to use CIL as a library to transform some C as part of a build process, targetting Visual C++. We can parse and transform the code, but when we serialise the transformed tree, the attributes are emitted in "__attribute__" form, rather than VC's __declspec form.
At the start of our driver program we have: open Cil;; Cil.msvcMode := true;; Frontc.setMSVCMode();; ... to try to tell the writer to output the MSVC form (which appears to be what cilly uses in the same situation). Can anyone give us some pointers on how to control the code generation? Thanks, Tom ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ CIL-users mailing list CIL-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cil-users
