Re: [Doxygen-develop] Re: Doxygen and C++/.NET

[Christian B. <chr...@am...>]

Allo Jason!

As a suggestion, you may want to try setting the PREDEFINED tag to some =
meaningful standard C++ definition for the Managed C++ keyword in =
combination with the ENABLE_PREPROCESSING, MACRO_EXPANSION and =
EXPAND_ONLY_PREDEF tags.

As an example, PREDIFINED tags were done for the boilerplate macros of =
the Microsoft's ATL and MFC libraries. You can find these definitions in =
the doxygen documentation under the Preprocessing heading.

I think this should get you going without the need for a code filter

Regards,

Christian
  ----- Original Message -----=20
  From: Jason Mills=20
  To: dox...@li...=20
  Sent: Monday, March 28, 2005 10:07 AM
  Subject: [Doxygen-develop] Re: Doxygen and C++/.NET


  Thanks for the response, but not exactly what I'm looking for. Maybe =
my=20
  question was not clear (... or you choose to answer it differently,=20
  which is fine :-) ). I'm looking to *use* Doxygen to create=20
  documentation for code written in Managed C++ and the upcoming =
C++/CLI.=20
  I'm not trying to compile Doxygen to work on the .NET platform, =
although=20
  that is cool.

  With the exception of your email, no one as responded to my original=20
  question. So I assume no one as used Doxygen with Managed C++. Thats a =

  pity. But I think Doxygen should support the upcoming C++/CLI. There =
is=20
  no doubt, it will be used significantly on the Windows platform.

  Thanks, anyway.

  Jason

  Hendy Irawan wrote:
  >   > Two few related questions:
  >   >
  >   > - Have anyone used doxygen with Managed C++ (.NET)? If so, are =
there
  >   >   any filters available to handle managed C++ keywords, such as
  >   >   __interface?
  >   >
  >   > - Will there ever be support for the soon to be available =
C++/CLI?
  >=20
  > I'm sure about the "users" point of view.
  >=20
  > But from the "develop" POV... I tried to do this:
  > - Compile doxygen as static lib (need to do some project =
configuration
  > changes here, I guess on most other dependent libs too)
  > - Create a Managed C++ project library/assembly
  > - Link that assembly with the static lib (need to do some project
  > configuration stuff, use "mixed mode" as opposed to pure IL)
  > - Export functions that you want in that assembly, that calls =
doxygen functions
  > - Create another "host" project in C#, references that Managed C++ =
assembly
  > - Call that assembly function in this host project
  >=20
  > It took some (a lot of) time to get it right. But when it's done, it
  > feels (kinda') great. "Hey, Doxygen running on .NET" ;-) It doesn't
  > parse .NET stuff, it just runs on .NET. :-)
  >=20
  > --
  > Hendy Irawan - http://dev.gauldong.net - GaulDong Developer Center
  >=20
  >=20



  -------------------------------------------------------
  SF email is sponsored by - The IT Product Guide
  Read honest & candid reviews on hundreds of IT Products from real =
users.
  Discover which products truly live up to the hype. Start reading now.
  http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
  _______________________________________________
  Doxygen-develop mailing list
  Dox...@li...
  https://lists.sourceforge.net/lists/listinfo/doxygen-develop