Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
@CVS Binary builders
Revy:
--- Quote from: thomas on November 23, 2005, 02:41:38 pm ---
--- Quote from: Revy on November 22, 2005, 05:52:39 pm ---Do you know Firefox? ;-)
--- End quote ---
Yes, but Firefox does not matter at all. What matters is Internet Explorer because it is a part of Windows.
It is of course always a problem to tell what is wrong especially on Windows systems where each and every program you install replaces a couple of dlls without telling you, and even Microsoft does not seem to know what is right sometimes.
All I can say is that two of us test on pristine installs of Windows98 systems with IE6, and it works. Maybe downloading a fresh copy of that dll will fix the problem.
--- End quote ---
I ignore that. ;)
--- Quote from: thomas on November 23, 2005, 02:41:38 pm ---
--- Quote ---Also you should have noticed, that I wrote "RC02 did run fine on W98" :?
--- End quote ---
Yes indeed, but I ignored that point because it makes no sense. RC2 is the most recent binary release. So what non-working binary release do you refer to, if RC2 is fine?
--- End quote ---
It does make sense, because it indicates that there is a problem with the cvs builds from Therion and Ceniza.
Sorry if i was a bit unclear about which CVS binaries I meant.
Ceniza:
I wonder if that function is needed by the trojans...
Oh, sorry, were you reading?
We'd need to compare the build environments for RC2 and the CVS snapshots. All I can say is I'm using the latest available stuff from MinGW and building wx with MSys.
Just like I said in another post: ~good to see there's a solution for it.
Revy:
--- Quote from: Ceniza on November 23, 2005, 06:07:29 pm ---I wonder if that function is needed by the trojans...
Oh, sorry, were you reading?
--- End quote ---
Yes, sorry - what did you say? :lol:
--- Quote from: Ceniza on November 23, 2005, 06:07:29 pm ---We'd need to compare the build environments for RC2 and the CVS snapshots. All I can say is I'm using the latest available stuff from MinGW and building wx with MSys.
Just like I said in another post: ~good to see there's a solution for it.
--- End quote ---
Revy:
Hello again,
i think the problem with SHGetFolderPath can be solved, SHFolder is added to the link libraries of the sdk target.
An alternative and imho better solution would be to change ConfigManager::GetConfigFolder() not to use SHGetFolderPath direct - e.g. change it to something like that:
--- Code: ---#include <windows.h>
#include <shfolder.h>
PFNSHGETFOLDERPATHA GetFuncPtr_SHGetFolderPathA()
{
static HMODULE hMod = NULL;
PFNSHGETFOLDERPATHA pSHGetFolderPath = NULL;
// Load SHFolder.dll only once
if (!hMod)
hMod = LoadLibrary("SHFolder.dll");
if (hMod)
// Obtain a pointer to the SHGetFolderPathA function
pSHGetFolderPath = (PFNSHGETFOLDERPATHA)GetProcAddress(hMod,
"SHGetFolderPathA");
return pSHGetFolderPath;
}
--- End code ---
The second solution has to be implemented by the devs though.
Solution 1 can be achieved by Therion and Ceniza. :)
Thx and bye
Revy
duncanka:
This issue still has not been resolved in any of the latest snapshots as of today. :( Is any solution in the works? Unfortunately, I'm stuck on a Win98SE computer, so I'm waiting here with bated breath...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version