User forums > Using Code::Blocks
Compiling a JNI file in Dev-C++ and Code::Blocks
Michael:
--- Quote from: jschwarz0 on December 09, 2005, 12:22:37 am ---wrap all jni available calls with
extern C
--- End quote ---
Unfortunately, even this does not solve the problem.
Michael
kostyabkg:
Yes, the same for me. However it's interesting that in Dev-C++ --add-stdcall-alias is already set in linker options! If I remove it I get the same bloody error with Dev-C++. Maybe it's worth turning to them (Dev-C++ team) and trying to found out, how they managed it to work?
As to me Dev-C++ remains the IDE of my choice. It's friendly for somebody new like me, has a very clean and clear interface. Lots of icons, that help me to remember what i should press to compile the program and what to run it. Also the most of my time I spend with Java, not C, so I need something comfortable to jump to for a few hours and back to Java.
That's something I wanted say about Code::Blocks - I know it's only 1 year old and has an amazing amount of possibilities for a 1 year old IDE, but in my opinion it needs to be a little more friendly to the user. I am sure it won't take much of a programming effort to create BIGGER buttons in a button panel. And also in drop down menus to put the same icon as on the buttons to make memorizing easier (just like they do it MS Office, Dev-C++, ....). I am sure it would attract much more newcomers and spread the popularity of this IDE.
I will be glad to listen to any other opinions.
Thank you very much for the amount of help I received!
I appreciate it, guys.
Michael:
--- Quote from: kostyabkg on December 09, 2005, 11:44:49 am ---Yes, the same for me. However it's interesting that in Dev-C++ --add-stdcall-alias is already set in linker options! If I remove it I get the same bloody error with Dev-C++. Maybe it's worth turning to them (Dev-C++ team) and trying to found out, how they managed it to work?
--- End quote ---
IMHO, the problem is a bit more complex. Even users of Dev-C++ have problems with JNI (see http://forum.java.sun.com/thread.jspa?threadID=570194&tstart=29):
--- Quote ---I am having some problems getting my DLL to work properly. I am following the basic Hello World example and seem to be getting a problem.
I am running on Windows XP with, j2sdk1.4.2_04, and using the gcc that comes with Dev-C++ (Bloodshed). The following is the steps I went through.
...
--- End quote ---
I think the problem is more from the compiler and/or JNI side, rather than from the IDE.
--- Quote from: kostyabkg on December 09, 2005, 11:44:49 am ---As to me Dev-C++ remains the IDE of my choice. It's friendly for somebody new like me, has a very clean and clear interface. Lots of icons, that help me to remember what i should press to compile the program and what to run it. Also the most of my time I spend with Java, not C, so I need something comfortable to jump to for a few hours and back to Java.
That's something I wanted say about Code::Blocks - I know it's only 1 year old and has an amazing amount of possibilities for a 1 year old IDE, but in my opinion it needs to be a little more friendly to the user. I am sure it won't take much of a programming effort to create BIGGER buttons in a button panel. And also in drop down menus to put the same icon as on the buttons to make memorizing easier (just like they do it MS Office, Dev-C++, ....). I am sure it would attract much more newcomers and spread the popularity of this IDE.
--- End quote ---
I do not agree with you, but I respect your choice. I have used Dev-C++ for sometime, but I have had problems e.g., in making it works (it worked in one computer, but not in another without apparent reasons :?). Moreover, it seems that its development is now over, but I may be wrong.
C::B is still young, but it progress fast and new features and/or improvements are added quite each day.
I find C::B user-friendly. Naturally, it needs sometimes to take confidence with the interface, but after 10 minutes I was able to work without many problems.
What is great it is also the possibility for me to compile my code using several compiler (useful for cross-platform developemnt).
Michael
kostyabkg:
Yes, I have noticed as well that somebody was having problems with Dev-C++.
Your opinion is very interesting, I was a bit cuirious why the latest Dev-C++ is of February of this year. It may seem funny or stupid, but the whole reason i started searching for a different IDE is because I found out that Dev-C++ is written in Delphi. There is nothing I have against Delphi, but... CodeBlocks seems to be more professional tool (at least in the future), than Dev-C++. That's why when I came across this error I didn't turn away and get back to Dev-C++, but posted this topic. I have the desire to use CodeBlocks, but I need it to produce correct DLL files or I can't work, so I have to stick with something working, because it's main priority for me.
However it would be grand if somebody could manage to get around this problem without rewriting def file and invoking compiler using the command line.
Is there somebody "Above", who would be able to go into the low-level things and get the solution?
Cheers,
Kostya.
Urxae:
I don't remember if there's a way to get Dev-C++ to show the complete command lines it uses when invoking the compiler and linker, but if there is then posting a log of a rebuild might contain enough information to help...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version