Forums > Dev

Win SDK: unresolved external symbol _systhread_init

June 15, 2006 | 12:53 pm

Hi,

I’m currently changing some code from using pthreads to the systhread
API. Since there’s no ducumentation about that one in the Writing
Externals PDF, so I’m gathering all my information from the
ext_systhread.h file….

There is a function systhread_init() declared, but when I try to use it
the linker says "unresolved external symbol _systhread_init". Should I
care? everything seems to work, but the presence of such a functions
makes me curious whether I should probably call it before using any if
the systhread functions.
Anyway, it’s a bug in the SDK that a function is defined but not exported.

Olaf


June 15, 2006 | 5:43 pm

I moved a sys_threaded project from mac to windows last week, and it
seems to work fine w/o calling systhread_init() before
systhread_create(). this is just my experience, but it seems ok so far.

best,
r.


June 15, 2006 | 6:16 pm

On Jun 15, 2006, at 5:53 AM, Olaf Matthes wrote:

> I’m currently changing some code from using pthreads to the
> systhread API. Since there’s no ducumentation about that one in the
> Writing Externals PDF, so I’m gathering all my information from the
> ext_systhread.h file….
>
> There is a function systhread_init() declared, but when I try to
> use it the linker says "unresolved external symbol
> _systhread_init". Should I care? everything seems to work, but the
> presence of such a functions makes me curious whether I should
> probably call it before using any if the systhread functions.

No you don’t need to call this function. It is called by the kernel +
has no need for export. It is harmless though if you do call it.

> Anyway, it’s a bug in the SDK that a function is defined but not
> exported.

Not necessarily. There are several functions in the headers but not
exported, since we share these files between internal and external
development rather than let them get out of sync by maintaining
independent copies.

-Joshua


June 15, 2006 | 6:20 pm

Joshua Kit Clayton wrote:

> Not necessarily. There are several functions in the headers but not
> exported, since we share these files between internal and external
> development rather than let them get out of sync by maintaining
> independent copies.

Okay, thanks for the info. I just found it confusing to find a function
there that looks to be important but can’t be used… :-)

Olaf


June 16, 2006 | 10:22 am

On 15-Jun-2006, at 20:16, Joshua Kit Clayton wrote:

>> Anyway, it’s a bug in the SDK that a function is defined but not
>> exported.
>
> Not necessarily. There are several functions in the headers but not
> exported, since we share these files between internal and external
> development rather than let them get out of sync by maintaining
> independent copies.

Completely understandable. A comment to that effect would be a help
for people trying to find their way, particularly if the .h file is
the principle documentation.

Just an idea. As maintenance allows.

– P.

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine +–> Litter Power & Litter Bundle for Jitter

iCE: Sequencing, Recording & |home | chez nous|
Interface Building for |bei uns | i nostri|
Max/MSP Extremely cool http://www.castine.de

http://www.dspaudio.com/


Viewing 5 posts - 1 through 5 (of 5 total)