Author |
Message |
Cheese Wow Cheese is so helpful!

Joined: Mar 18 2007 Posts: 1017 Offline
|
Posted: Fri Dec 19, 2008 1:18 am Post subject: yet more module compile issues |
 |
|
|
|
tcsoccerman wrote: |
I think that it would be appropiate for someone to make a sticky on the steps too compiling a clean asss 1.4.4 on windows.
|
looked at the other sticky, didnt help at all...
not trying to compile the entire core, just a simple hello world module...
downside: im compiling under dev-c++ v4.9.9.2 in windows.
managed to get the errors down to a minimum, here they are:
[img][/img]img down till later
--edit--
looks like its missing
#include "packets/login.h"
because
#include "packets\login.h"
is correct?
still wierd because i fixed it with
#include "..\packets/login.h"
player.h
#include "..\packets/pdata.h"
#include "..\packets/ppk.h"
#include "..\packets/login.h"
defs.h
#include "sizes.h"
#include "..\packets/types.h"
#include "..\packets/simple.h"
core.h
#include "..\packets/login.h"
--edit2--
managed to compile a dll by commenting out 90% of the code, and raping my asss src files, and then got shot down by a
"
I <cmod> loading C module 'mine' from 'mine'
E <cmod> error in GetProcAddress: The specified procedure could not be found.
Unrecoverable error (5): Error in loading module 'mine:mine'
"
i know its named mine.dll, but where do i find the mine:whatever part?
<loader>file:modname
loader and file are easy to guess, but where do we find modname if we compile in windows?
--edit3--
followed steps in
http://wiki.minegoboom.com/index.php/Installing_New_Modules
made compile nice and easy, once i took out util from the project.
still cant find the mine:whatever though
--edit4--
would it matter if it was a c++ project in dev-c++ instead of a regular c one?
if it helps:
i can get a empty module to compile, but when i try to use
chat=mm->GetInterface(I_CHAT,ALLARENAS);
i get
invalid conversion from `void*' to `Ichat*'
END ASSS DAY 1 _________________ SSC Distension Owner
SSCU Trench Wars Developer
Last edited by Cheese on Sun Dec 21, 2008 5:06 pm, edited 4 times in total |
|
Back to top |
|
 |
cmdrpinksock Novice
Age:44 Gender: Joined: Dec 05 2008 Posts: 43 Location: Fort Worth Offline
|
Posted: Fri Dec 19, 2008 10:53 am Post subject: |
 |
|
|
|
Same here... |
|
Back to top |
|
 |
CaptainPoopface Newbie

Joined: Dec 16 2008 Posts: 17 Offline
|
Posted: Fri Dec 19, 2008 11:52 am Post subject: |
 |
|
|
|
Yeah, I am also having the same problem, trying to compile various simple modules on a linux server.
I'm wondering if it's something funny in the makefile, or something about the 1.4.4 build, or just a stupid mistake... |
|
Back to top |
|
 |
Cheese Wow Cheese is so helpful!

Joined: Mar 18 2007 Posts: 1017 Offline
|
Posted: Fri Dec 19, 2008 5:37 pm Post subject: |
 |
|
|
|
there is no detailed information regarding the module compile process,
and even less information regarding the module loading process...
and until i can successfully compile -1- working module, all progress in my development comes to a halt.
and i have people waiting. |
|
Back to top |
|
 |
Dr Brain Flip-flopping like a wind surfer

Age:39 Gender: Joined: Dec 01 2002 Posts: 3502 Location: Hyperspace Offline
|
Posted: Sat Dec 20, 2008 4:04 pm Post subject: |
 |
|
|
|
Yes, it matters if it's a C++ project. Making it a C project should fix that void* to Ichat* issue (that's one of the few C++ backwards incompatibilities).
As for the #include issue, you probably don't have some include directory that it wants. I suggest adding the asss/src directory to the list of include directories.
What's your load function called? MM_mine? If it's MM_abcd, and part of mine.dll, you use mine:abcd to load it. The second half MUST be the same as the load function's name. _________________ Hyperspace Owner
Smong> so long as 99% deaths feel lame it will always be hyperspace to me |
|
Back to top |
|
 |
Cheese Wow Cheese is so helpful!

Joined: Mar 18 2007 Posts: 1017 Offline
|
|
Back to top |
|
 |
|