[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kdoc
Subject:    RE: KDOC & Windows NT
From:       Mike Davis <mdavis () xcaliber ! com>
Date:       2000-04-28 7:56:45
[Download RAW message or body]

Thanks for the reply...

I do #define DLL_EXPORT like you write and it's WIN32 for the OS, btw.

I didn't think I'd be able to pass it through the pre-processor of developer
studio as I was under the impression that KDOC only worked with gcc. I've
just tried it with "cl" but it complained about a missing DLL, what a
suprise!

I've decided to fetch CygWin and the GNU compiler instead but if someone can
help me out with the MS compiler (especially from the IDE) I'd be grateful
as I have to share my projects with other (NT) developers. I figured a post
build process or a different target for documentation would be the way to
go.

-----Original Message-----
From: Marc.Roth@energie.rwe.de [mailto:Marc.Roth@energie.rwe.de]
Sent: Thursday, April 27, 2000 6:33 PM
To: mdavis@xcaliber.com; kdoc-list@master.kde.org
Subject: RE: KDOC & Windows NT


Mike,

First, you should define your DLL_EXPORT macro as follows (_WIN32 should be
defined if you use MSVC++ otherwise you must define it in your makefile's
CPPFLAGS as -D_WIN32)

#ifdef _WIN32
#	ifdef LIBRARY_EXPORTING
#		define DLL_EXPORT	__declspec(dllexport)
#	else
#		define DLL_EXPORT	__declspec(dllimport)
#	endif
#else
#	define DLL_EXPORT
#endif

When you run your header files through kdoc you need to force it to pass the
files first through the c-preprocessor like by using command line option
--cpp
To specify where your c-preprocessor can by found on your system and what
arguments/options it needs you can use command line option `--cppcmd
<command>'.
Because this option didn't work with my version of kdoc (2.0a35) I needed to
tweak the value of the $defcppcmd in the kdoc perl script directly.

hope this helps

Marc

> -----Original Message-----
> From:	Mike Davis [SMTP:mdavis@xcaliber.com]
> Sent:	Thursday, April 27, 2000 5:15 PM
> To:	'kdoc-list@max.tat.physik.uni-tuebingen.de'
> Subject:	KDOC & Windows NT
> 
> I got a copy of Active Perl and the latest KDOC 2 alpha. Since NT has
> issues
> with shared libraries and classes I have to put an export between the
> class
> and class name. For example...
> 
> class DLL_EXPORT MyClass {
> };
> 
> I #define the DLL_EXPORT to mean export when building or import when
> using.
> 
> KDOC has (naturally) problems with the syntax. Is there anyway to get
> around
> this so that I can easily generate documentation? Oh, I'm using Developer
> Studio.
> 
> M.

[prev in list] [next in list] [prev in thread] [next in thread]