csjava.dll wanted | linker problem (?)

[Sp4M]

Hi,

I tried to generate csjava.dll (I would use CS in java on windows).
I built CS on linux with configure/jam, everything is now ok (0 error) and I get the crystalspace.jar
I built CS on windows with VS Express C++ 2008 with msvc9 solution, everything build (0 error)
but still no trace of csjava.dll ...

Project (SimpleRoom) run on Eclipse (with .jar linked) gives :

Code:

Loading CrystalSpace library
Fatal Error: unresolved symbol in 'csjava'.
java.lang.UnsatisfiedLinkError: no csjava in java.library.path

- Version of CS : 1.4.0
- Version of winlibs package : cs-win32libs-1.4_002
- Operating system : Win7
- Compiler : VS Express 2008

Any idea ?

[duodenum]

Can you place your all code here. I will try it on my com & fixit for you.

[Sp4M]

I didn't really generated many code for now, it doesn't work at the beginning with this :
(SimpleRoom.java is unchanged code from CS)

Code:

public class Main {
public static void main(String[] args) {
new SimpleRoom();
}
}

I think the problem is from Eclipse configuration for CS. Again, I don't have any csjava.dll ...

[Sp4M]

am I the only one to use cystalspace on windows with java ... ?

[Sp4M]

I probably found a part of the solution by myself. (my problem is still to obtain csjava.dll file)

when I run the configure script, it gives me

Code:

...
checking if --kill-at is accepted... no
...

But configure file says

Check if linker recognizes --kill-at which is needed to make csjava.dll

after investigations in config.log, we can read

Code:

configure:18376: checking if --kill-at is accepted
configure:18477: g++ -o conftest     -Wl,--kill-at   conftest.cpp   -lnsl -lc  >&5
/usr/bin/ld: unrecognized option '--kill-at'
/usr/bin/ld: use the --help option for usage information

in fact, the /usr/bin/ld command does not actualy recognize the --kill-at, but the /usr/i586-mingw32msvc/bin/ld does.
But how tell the g++ to check the "correct" linker here ?

[Sp4M]

(No i'm not flooding !)

Update : in fact the default linker does recognize the --kill-at option, but :

   --kill-at
           If  given, the stdcall suffixes (@nn) will be stripped from symbols
           before they are exported.  [This option is specific to the i386  PE
           targeted port of the linker]

and

Code:

uname -m

gives

i686

could be a problem there, isn't it ?

[kickvb]

Sorry, I'm not able to help you.
But maybe you would try asking your question on the mailing list or the irc, the developers that can probably answer to this are more active on these communication channels.