Programming Forums - View Single Post

Kaja Fumei · Jan 9th, 2006, 6:35 PM

I updated the source. A bunch of bug fixes, and improved ways of doing things. And imports work

Anything imported into a DLL will automaticly be imported into the program. But there still is a problem: any Windows function that makes an OS system call/interrupt call will of course not work on linux (still works on windows). But it imported Windows' strlen without a problem.

Same address but I'll post it again: http://www.entertheunknown.net/proje...pso_source.zip

Mad_guy, this is just a stepping stone. I'm not trying to bring the Windows API to unix and I'm not trying to make another WINE. I would go crazy trying. The goal is to make a new format (call it pso) or possibly extend another one, so that I could import a library successfully on unix and windows if the same processor. Say I want to make, for example, a string library to be used as a module in my virtual machine. If I'm feeling lazy, the library will almost definitely make use of some string.h function; let's just say it's strlen. I want to be able say to windows to fetch msvcrt.dll for strlen and fetch libc.so on unix. Granted, this would take a lot more work than a new or extended format. At the very least, a whole new linker program. It's going to be a fair amount of work, but not the life commitment of trying something like WINE.

Jan 9th, 2006, 6:35 PM	#6
Kaja Fumei Hobbyist Programmer Join Date: Oct 2005 Posts: 134 Rep Power: 3	I updated the source. A bunch of bug fixes, and improved ways of doing things. And imports work Anything imported into a DLL will automaticly be imported into the program. But there still is a problem: any Windows function that makes an OS system call/interrupt call will of course not work on linux (still works on windows). But it imported Windows' strlen without a problem. Same address but I'll post it again: http://www.entertheunknown.net/proje...pso_source.zip Mad_guy, this is just a stepping stone. I'm not trying to bring the Windows API to unix and I'm not trying to make another WINE. I would go crazy trying. The goal is to make a new format (call it pso) or possibly extend another one, so that I could import a library successfully on unix and windows if the same processor. Say I want to make, for example, a string library to be used as a module in my virtual machine. If I'm feeling lazy, the library will almost definitely make use of some string.h function; let's just say it's strlen. I want to be able say to windows to fetch msvcrt.dll for strlen and fetch libc.so on unix. Granted, this would take a lot more work than a new or extended format. At the very least, a whole new linker program. It's going to be a fair amount of work, but not the life commitment of trying something like WINE.