Recompiling .DLL from FB11 to FB13

[Dean]

I'm having a little trouble recompiling .13b that compiles in .11 and
could use a hand on what I'm doing wrong or forgot to do.

I did notice the difference in the mydll.bas sample with .13 as to:
#ifdef __FB_WIN32__ , which used to be #ifdef FB__WIN32 in .11.

And I did change that in my original dll .bas code, which
eliminated one error I was getting as to file not found when
compiling with .13b. But I still get the following error:

C:\FB13\FREEBA~1\bin\win32\dlltool.exe: Syntax error in def file mydll2.def:0

I've copied all the original dll files to the new fb13 folder (i.e.,
.bas, .bi, .a, but .13b still gives me the above syntax error whereas
.11 does not. I get this same error as well if I simply try to compile
the old mydll.bas that came with .11 under .13.

I think I have to do something with pexports? Could use a hand.

Dean

[v3cz0r]

Are you building the DLL under the same directory where the mydll.bas? That errors happens when the path is not stripped (what was fixed since version 0.11 or such) or when the dll name contains dots, minus or anything but alpha-numeric characters (a dlltool limitation).

[Dean]

With FB11, all the files are in the same folder

c:\freebasic

Those files are mydll2.bas, mydll2.bi, libmydll2.dll.a

FBC -dll mydll2.bas compiles in that folder with 0.11b with no errors.
There are no dots or non-alphanumeric characters as you can see
by the file names.


I then copied all those files to the new folder where 13b is

c:\FB13\freebasic

And I tweaked the .bas file for the change to #ifdef __FB_WIN32__

But then FB13 gives that error I mentioned.

I did the same with the unedited mydll.bas that came with FB11,
and I get the same error.

I also tried putting the fbc 0.13b exe in the original folder
c:\freebasic, where the original files are and which get compiled
okay with 0.11b, but 0.13b still generates errors in that folder.

???????

Dean

[v3cz0r]

No idea, i updated the dlltool to the lastest version in 0.13, but it seems to work fine here.