And it works with a resource folder designated. I just had to drop the .dylib
extension.
All seems to work. I'm guessing it was a bad library file.
> On Apr 15, 2016, at 10:19 PM, Dar Scott wrote:
>
> Thanks, all!
>
> I got this to work. I'm able to load a dynamic library in LiveCode B
Thanks, all!
I got this to work. I'm able to load a dynamic library in LiveCode Builder.
I don't know what the problem was. My last change switched to a different
library and used a much shorter line (simpler function). I also used a full
path; that worked with both a simple 'load extensio
A utility named file sees both 32 and 64. The utility lipo sees 64.
I'm suspecting dependencies. This isn't my .dylib file.
I'm wondering if there is a way I can check dlerror() somehow.
> On Apr 14, 2016, at 9:41 PM, Monte Goulding wrote:
>
> It's 32 bit?
>
> Sent from my iPhone
>
>
It's 32 bit?
Sent from my iPhone
> On 15 Apr 2016, at 1:07 PM, Dar Scott wrote:
>
> Thanks, Monte!
>
> However, I still have the same error message, so my problem seems to be
> something else.
>
> I poked at it a bit.
>
> The error message seems to be in script-instance.cpp. Looking at
Thanks, Monte!
However, I still have the same error message, so my problem seems to be
something else.
I poked at it a bit.
The error message seems to be in script-instance.cpp. Looking at that, it
seems that dlopen is used. I don't have environment variables for dlopen, the
best I can
Thanks! I'll move it there. I will need to remove the copies everywhere else
once that works.
> On Apr 14, 2016, at 5:30 PM, Monte Goulding wrote:
>
> Hi Dar!
>
> The dylib should be found if it is in resources/code/mac/
>
> // This is the callback given to libscript so that it can resolv
Hi Dar!
The dylib should be found if it is in resources/code/mac/
// This is the callback given to libscript so that it can resolve the absolute
// path of native code libraries used by foreign handlers in the module. At
// the moment we use the resources path of the module, however it will need
I want to see the "Widgets by Dar" collection, too! I'm not sure if I want the
snap-together widgets or the "who needs LabView when you have LiveCode" widgets
first. I might start with some libraries.
And I still haven't solved the issue with this error message. I've tried
putting my dynam
Now all he needs is someone who knows the answer.
I'm looking forward to seeing the "Widgets By Dar" collection. :)
On 4/14/2016 2:24 PM, Jim sims wrote:
It's Dar!
He Lives! He's Alive! Alive!!
On Thursday, April 14, 2016, Phil Davis wrote:
My sentiments exactly!
Phil Davis
On 4/14/16
It's Dar!
He Lives! He's Alive! Alive!!
On Thursday, April 14, 2016, Phil Davis wrote:
> My sentiments exactly!
>
> Phil Davis
>
>
> On 4/14/16 12:00 PM, J. Landman Gay wrote:
>
>> On 4/14/2016 1:34 PM, Dar Scott wrote:
>>
>>> Dar "I'm back" Scott
>>>
>>
>> Yay!
>>
>>
> --
> Phil Davis
>
>
>
My sentiments exactly!
Phil Davis
On 4/14/16 12:00 PM, J. Landman Gay wrote:
On 4/14/2016 1:34 PM, Dar Scott wrote:
Dar "I'm back" Scott
Yay!
--
Phil Davis
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to
On 4/14/2016 1:34 PM, Dar Scott wrote:
Dar "I'm back" Scott
Yay!
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
___
use-livecode mailing list
use-livecode@lists.run
I'm using LiveCode Builder in LC 8.0.0-rc-1 on Yosemite.
I am getting the error "unable to load foreign library" on the first try of a
call to a foreign handler.
I am guessing that I don't have the .dylib in the right place. It is a couple
folders down in a folder I p
13 matches
Mail list logo
