i need some explanation so i hope somebody knows ...
I downloaded SQLITE source from http://system.data.sqlite.org compiled it with build flags not to use interop, so i can use it with mono on linux.
On Linux + Mono the built assembly works without a problem... But on windows it says that it needs SQLITE3.dll.
Now my question is why? Should it be created completley managed without the need of sqlite3.dll ? or am i mising something?
And we will not be building for windows with mono :D so Mono.data.sqlite is out of the question.
Best regards,
Lonko
It is not completely managed, on Windows, you need to supply sqlite3.dll with the binary.
See here:
System.data.sqlite homepage: FAQ, question 11
Related
I am working on a compiler for a small (toy) language that produces 16-bit com-files, which are executable in Windows XP. However, in more modern releases of Windows com-files are executable only with the help of tools such as DosBox. I would like my compiler to produce exe-files that can be executed directly in Windows 10.
As I understand it, the exe-file needs a header that instructs the system of how to execute it. My idea is to simply add the header at the beginning of the com-file to extend it into an exe-file. I wonder if anyone can recommend an appropriate tutorial that describes how exe-files works. More specifically, I am looking for a tutorial of how to build the smallest possible working exe-file.
I also wonder if there is a difference between exe-files for 32-bit or 64-bit Windows?
Best Regards,
Stefan
You can download description exe format here. You need pecoff.docx file.
Also you may look on this old but detailed doc here.
Is there a way of using libraries built in Linux on Windows, without porting and rebuilding them?
The short answer is "No". Although there is a way of doing that vice-versa (via WINE).
That would require loading ELF binaries. Extending the loader in Windows seems to be difficult if not impossible, going by the answers to this question:
Is it possible to replace Loader of an OS? Any way to obtain the control over Loader?
I'm looking for a .chm creator on Mac, but can't seem to find one? There seems to only be .chm readers for OS X.
Are there any .chm creators for OS X?
Thanks
Probably not, because .chm files are specific to Windows, and are deprecated even there. Are you trying to produce Apple Help files? If so, check out the Apple Help Programming Guide.
Yes. The Free Pascal compiler has a creator library, which also should work on Mac.
Note that this is just a chm compiler, iow something that compiles .html (and .hhc/.hhk/.hhp) into a .chm.
The library is already in current editions of the Free Pascal project (2.4.2). A commandline frontend (a chm compiler that understands .hhp) is currently only in development releases (but will go live in the current months in 2.4.4 and 2.6.0)
Update: the commandline compiler is now live in 2.6.0. It doesn't support all features (like merging chms)
In Windows Vista, Microsoft introduced new functions for power management in the Windows API.
These are usually included by #include <PowrProf.h>. The Problem is, that the Qt SDK 2010.05 uses MinGW with an outdated version of PowrProf.h. That’s why you cannot, for example, use the function PowerEnumerate.
Which would be the proper way to make the Qt SDK ‘speak’ the new functionality?
Thank You,
Paul
I know it's not the easiest solution, but you could always download the Windows SDK and grab the latest header file from there. (I just checked v7.0a and it does indeed have 'powrprof.h'.)
I haven't tried this, but you may be able to simply swap the new version of the header with the old version that ships with Mingw32. You will probably have to link with the new version of the library too ('powrprof.lib').
I need to support Windows 98. The Qt documentation claims this is possible, but there are no instructions. The distributed binaries of Qt 4.6 don't run on Win98 and the majority of Qt applications I have sampled also don't. For several apps that do run on 98, I have asked authors how they did it, but the common answer is that it was accidental and they don't know what factors caused it.
In searching the forums for help, I found only guesses that turned out to be wrong. For example, one belief is that to compile for Win9x, you must build the tools and the apps on that platform. Yet, things I found to run were built on newer versions of Windows.
What is required to build the Qt dev tools and then applications for Win98?
How about cross-compiling from WinXP or Linux?
Are there specific components that can't be made to run on Win98?
Are there particular difficulties with dynamic or static linking for Win98 support?
Here is as far as I'm going to get on this:
You can target Windows 98 using MinGW or VC++ 6 SP5 from any Windows version. Cross-compiling from Linux is doable but not easy to set up.
Qt 4.4.3 was the last version officially tested on Win98. To run the distributed binaries on Win98, you need to install older versions of glu32.dll and opengl32.dll that are available from Microsoft. Due to an unresolved bug, Assistant will launch but can't load the help files. The alternate version in the bin directory, assistant_adp.exe, works fine. It seems the only other potential problem is that QtOpenGL may use features not available on older boxes.
Qt 4.5.3 appears to be still compatible except for WebKit, OpenGL, and Phonon. QtOpenGL expects OpenGL 1.5, which I don't know is even possible on older boxes. I didn't look into Phonon deeply enough to see exactly what the problems are. QtWebKit now requires Win2K or better. The distributed binaries work mostly OK. Assistant depends on QtWebKit, so will not launch, but assistant_adp.exe still works.
Qt 4.6.3 distributed binaries are now completely incompatible with Win98. It may be possible to get some things working with MinGW 4.4 and a lot of hacking.
Building Qt Creator requires Qt 4.6.0 and either MinGW 4.4 or VS 2008.
Wow...interesting mission.
So, basically - yes, there is windows 98 support for Qt. The problem is that there is one big IF. For example if you even try to set some different QTextCodec::codecForName, you'll have to provide 3rd party ttf for this purpose, because in most cases Win98 will not recognize it as valid. If you provide the exact error, while compiling it on win98 machine, I could help you.
"How about cross-compiling from WinXP or Linux?" - If you use ONLY Qt libraries everything goes fine. Otherwise in .pro file, you have to link these libs under win32 and unix conditions. So you could even forbid your code, to be compiled and executed in other systems...
"Are there specific components that can't be made to run on Win98?" - Of course. In .pro file you could include different libraries, for different operating systems.
"Are there particular difficulties with dynamic or static linking for Win98 support?" - As far as I know - there isn't.
//off - But it still strange, that someone want to write application for win98, today...