Hi Kim,
On Sat, May 17, 2008 at 5:44 PM, kim aldis <xsi(at)kim-aldis.co.uk> wrote:
> #ifdef unix
> Extern C
> #endif
>
> But if it were that it would affect the 32 bit build, wouldn't it?
No, but it may be that the compiler isn't name mangling in 32bit where it is
in 64bit. Add
extern "C"
in front of the functions is needs to find to register or whatever the entry
point is called. My guess is that'll sort your issues, but given I know next
to nothing about windows it could be something entirely different.
Cheers,
Alan.
>
>> -----Original Message-----
>> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
>> Behalf Of Alan Jones
>> Sent: 17 May 2008 17:21
>> To: XSI(at)Softimage.COM
>> Subject: Re: package location workflow
>>
>> The 64bit complier is name mangling when it shouldn't? Have you got the
>> entry point declared extern "C" ?
>>
>> Cheers,
>>
>> Alan.
>>
>> On Sat, May 17, 2008 at 12:43 PM, kim aldis <xsi(at)kim-aldis.co.uk>
>> wrote:
>> > Yeah, it's working well for me thanks Thiago.
>> >
>> >
>> >
>> > Except, I do have a problem with an old style compiled plugin that
>> won't
>> > work in 64 bit XSI:-
>> >
>> >
>> >
>> > Plugin.32.dll, works in xsi 32
>> >
>> > Plugin.64.dll, doesn't work in xsi 64, can't find the entry point.
>> >
>> >
>> >
>> > Anyone seen this before?
>> >
>> >
>> >
>> > From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
>> Behalf Of
>> > Thiago Costa
>> > Sent: 16 May 2008 18:18
>> > To: XSI(at)Softimage.COM
>> > Subject: Re: package location workflow
>> >
>> >
>> >
>> > Hey Kim,
>> > I think the best way to do it is in the plugin manager, right-click
>> in the
>> > addon folder and "package location".
>> >
>> > If you have a HTML help with images, you need to look the XML header
>> in the
>> > XSIaddon file. Here it keep the path to your local folder so it won't
>> work
>> > when you install your addon in another machine.
>> >
>> > I see you find the answer already but I thought I should mention
>> these.
>> >
>> > 2008/5/16 kim aldis <xsi(at)kim-aldis.co.uk>:
>> >
>> > Never mind, I found the relevant section and the veils have been
>> lifted from
>> > mine eyes.
>> >
>> >
>> >
>> > From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
>> Behalf Of
>> > kim aldis
>> > Sent: 16 May 2008 13:54
>> > To: XSI(at)Softimage.COM
>> > Subject: package location workflow
>> >
>> >
>> >
>> > Would someone explain the intended package location workflow for me?
>> I'm
>> > unclear. My perception of it before I tried it was that I stuffed all
>> my
>> > relevant plugins into a folder then pointed package location at that
>> folder
>> > but on looking it appears the source folder can only be in an addons
>> > directory. One wouldn't normally place plugins in an addon directory
>> so this
>> > suggests you either have to move plugins there or package them up
>> into there
>> > first, which kind of defeats the object, doesn't it?
>> >
>> >
>> >
>> > What am I missing?
>> >
>> >
>> >
>> > Ta.
>> >
>> >
>> >
>> >
>> >
>> >
>> ---
>> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
>> body:
>> unsubscribe xsi
>
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
> unsubscribe xsi
>
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
