This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Why does this __declspec(dllimport) fail to compile?

To: cygwin at sources dot redhat dot com 
Subject: Why does this __declspec(dllimport) fail to compile? 
From: Mo DeJong <mdejong at cygnus dot com> 
Date: Thu, 9 Aug 2001 02:10:53 -0700 (PDT) 


The code does compile if use G++.  I think the FAQ you cite says that
MSVC++ also needs to compile as C++

This function is provided by G++ to do the job:
/* The name of the function we create to handle initializations and
   destructions for objects with static storage duration.  */
#define SSDF_IDENTIFIER "__static_initialization_and_destruction"

Mo DeJong wrote:


I have run into a little problem with a static initializer
that seems to work just fine with VC++ but fails with gcc.

% cat callback.c 
extern __declspec(dllimport)
void ExtCallback(void);

typedef void (callback) (void);

typedef struct Scallback {
} Scallback;

static Scallback scall = {ExtCallback};

int main() {
    callback*sc = scall.c1;
    return (int) sc;

% gcc -c callback.c
callback.c:10: initializer element is not constant
callback.c:10: (near initialization for `scall.c1')

When this same code it compiled with VC++ it waits
until link time to figure out the function address.

Why does this fail with gcc?


Other folks have mentioned this python FAQ but
it does not explain why gcc generates this error.

_____________________________________________________________________________ - Father's Day Shopping
- Find the perfect gift for your Dad for Father's Day

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]