It's being compiled as a dll -- any idea what would get it to complain about "Assuming console"?
I figure the "string" is really a userlib that is not compatible with 4.6?
DLL not compiling...
DLL not compiling...
It's being compiled as a dll -- any idea what would get it to complain about "Assuming console"?
I figure the "string" is really a userlib that is not compatible with 4.6?
Re: DLL not compiling...
Maybe you have a userlib that only works in ascii mode, but your dll is compiled in unicode mode? I'm just guessing here.
-
IdeasVacuum
- Always Here
- Posts: 6426
- Joined: Fri Oct 23, 2009 2:33 am
- Location: Wales, UK
- Contact:
Re: DLL not compiling...
....Possibly the Compiler Options Library Subsystem field is empty but should contain something like UserlibUnicodeThreadsafe. Also, the Executable format combo set to Shared DLL?
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
If it sounds simple, you have not grasped the complexity.
Re: DLL not compiling...
which means, every userlib using the FindString() function has to be recompiled for pb 4.60.PB 4.60 wrote:- Changed: FindString() 'StartPosition' parameter to be optional
c ya,
nco2k
If OSVersion() = #PB_OS_Windows_ME : End : EndIf