search

waneck / testrepo

0 stars 0 forks source link

Issue 1056 - Haxe/Neko cannot find library on Windows - haxe #1056

Closed waneck closed 11 years ago

waneck commented 11 years ago

[Google Issue #1056 : http://code.google.com/haxe/issues/detail?id=1056] by joshuagr...@gmail.com, at 2012-07-17T05:47:20.000Z When NME is installed to "C:\Motion-Twin\haxe\lib\nme\3,4,0", the command-line tools are unable to find "tls.ndll"

This does not occur on Windows for a development directory (at least, the directories I have used), and does not occur on Mac or Linux.

When I copied the file to "C:\Motion-Twin\haxe\lib\nme\3,4,0" instead of "C:\Motion-Twin\haxe\lib\nme\3,4,0\ndll\Windows" it was able to find the file. For some reason it could not find the file where it was.

waneck commented 11 years ago

[comment from ncanna...@gmail.com, published at 2012-07-17T08:36:06.000Z] Could you print the following in your commandline tool before loading tls.ndll ?

Sys.println(untyped $loader.path)

This will give you the paths that are used to lookup NDLL files

waneck commented 11 years ago

[comment from ncanna...@gmail.com, published at 2012-07-17T09:20:43.000Z] I'm not sure I understand your scenario.

A few things to check + explanations :

a) at compile time, make sure that haxelib find the ndll directory. You can try to run the following command : haxelib path It should print a -L

if it find a ndll directory

should be a relative directory ! b) at runtime, neko boot will add to its seach path : (HAXELIB)//(System)[64]/ HAXELIB = auto detect haxelib path = the one we had at compilation (System) = the current system string 64 = if we are running in 64 bit mode
waneck commented 11 years ago

[comment from ncanna...@gmail.com, published at 2012-07-26T14:38:23.000Z] The actual issue was that the path used for NDLL lookup is not the lib/version/ndll when in dev mode, but the absolute path to the dev/ndll directory.

Two possibilities here :

a) leave it as-it

b) makes "haxelib path" print two lookup paths : the absolute one for /dev/ and then the normal (haxelib)/lib/version by extracting the version from dev/haxelib.xml

waneck commented 11 years ago

[comment from ncanna...@gmail.com, published at 2012-07-28T13:28:55.000Z] This is a bit a particular case so I will not take action on it until someone else also come up with a similar issue.