View previous topic :: View next topic |
Author |
Message |
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Fri Mar 10, 2017 2:07 pm Post subject: Problem with subroutine in C |
|
|
In my project I use a small subroutine written in C. This routine calls GlobalLock and GlobalUnlock. It will be compiled with the SRC compiler.
If I compile and link my project with the new FTN95 8.10 in 32-bit mode SDBG reports missing symbols GlobalLock and GlobalUnlock.
If I compile and link my project in 64-bit mode everything works fine.
Until FTN95 7.xx I had no such problem with 32-bit. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Fri Mar 10, 2017 2:11 pm Post subject: |
|
|
These are the compilation opten for the C subroutine:
32-bit: SCC SET_MFP.C /ANSI_C /PROTOTYPES /WINDOWS /BINARY $(OBJ)\SET_MFP.OBJ
64-bit: SCC SET_MFP.C /64 /ANSI_C /PROTOTYPES /WINDOWS /BINARY $(OBJ)\SET_MFP.OBJ |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Fri Mar 10, 2017 5:01 pm Post subject: |
|
|
The C code will be compiled by SCC and (for 32 bits) linked via SLINK.
It is SLINK that reports the missing routines.
GlobalLock and GlobalUnlock are in kernel32.dll and this library is automatically scanned by SLINK.
If you can reduce the build process to simple steps and provide more details then I might be able to work out what is going wrong. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Sat Mar 11, 2017 10:57 am Post subject: |
|
|
Of cause I meant SLINK and SLINK64 not SDBG and SDBG 64.
I will try to build a small example. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Mon Mar 13, 2017 9:56 am Post subject: |
|
|
I have reduced my large project to a small example now, which produces the problem still.
How can I send this example? |
|
Back to top |
|
|
|