|
Subscribers H/PC Guru Posts: | 5,661 |
Location: | United States | Status: | |
| And I defined the exact directory of the libraries |
|
|
|
Administrator H/PC Oracle Posts: | 17,950 |
Location: | United Kingdom | Status: | |
| Quote torch - 2023-01-12 9:48 PM
I compiled as mfc instead of not mfc that'll do it |
|
|
|
Subscribers H/PC Guru Posts: | 5,661 |
Location: | United States | Status: | |
| Quote I dunk for bananas - 2022-12-11 10:58 AM
I got it all set up! Sadly I wasn't able to get any further with our gx.dll, it's either the same result as before or I get an illegal application error. As for itaskmgr, it seems like the toolhelp.lib we have for x86 isn't compatible with it at all and I get linking errors
I just uploaded an x86 fork of itaskmgr. Check it out. It may compile for ce5 and it’s open source
https://www.hpcfactor.com/scl/1933/datadiode/ITaskMgr/version_1.0.3Edited by torch 2023-01-13 1:21 AM
|
|
|
|
H/PC Elite Posts: | 685 |
Location: | Europe | Status: | |
| That's a great find! I tried running all of the builds on my CE5 device but they all result in errors. Sadly I don't have enough knowledge about how we would go about targeting CE5 with the supplied sources |
|
|
|
H/PC Elite Posts: | 685 |
Location: | Europe | Status: | |
| Tried compiling the unzip.dll but it's giving me this:
Linking...
Creating library X86Rel/unzip.lib and object X86Rel/unzip.exp
LINK : error LNK2001: unresolved external symbol __DllMainCRTStartup
maketree.obj : error LNK2019: unresolved external symbol _exit referenced in function _maketree
X86Rel/unzip.dll : fatal error LNK1120: 2 unresolved externals
Error executing link.exe.
unzip.dll - 3 error(s), 2 warning(s) |
|
|
|
Subscribers H/PC Guru Posts: | 5,661 |
Location: | United States | Status: | |
| You’re getting the same errors as me. Once we solve it I’m sure we’ll be able to compile more stuff haha |
|
|
|
Factorite (Senior) Posts: | 84 |
Location: | Japan | Status: | |
| I just downloaded Unofficial UnZip.dll for Windows CE 0.93.01, built for x86 with CE 4.0 Standard SDK on eVC4, and attached what I got to this post. Are these what you want? Edited by watamario15 2023-01-14 8:09 AM
Attachments ---------------- unzip_eng.zip (36KB - 2 downloads) unzip.zip (36KB - 1 downloads) |
|
|
|
Subscribers H/PC Guru Posts: | 5,661 |
Location: | United States | Status: | |
| Quote
Thank you for doing that. Is it okay if I add that to the SCL and add a comment saying “x86 versions compiled by watamario15” |
|
|
|
Factorite (Senior) Posts: | 84 |
Location: | Japan | Status: | |
| No problem! |
|
|
|
H/PC Elite Posts: | 685 |
Location: | Europe | Status: | |
| Awesome, that's exactly them! Thank you so much!
Did you change anything other than the target platform before you compiled it? |
|
|
|
Subscribers H/PC Guru Posts: | 5,661 |
Location: | United States | Status: | |
| So here’s the deal.
There was a user here by the name of TFGBD who was able to compile a bunch of programs for x86 and I want to eventually try and knock it all out.
How do you fix those linking errors because I don’t want to have to bother you to compile them all? Haha. Plus I’d like to learn because I feel like I’m missing a small step but a very important one.
That link is here under the open source area:
https://web.archive.org/web/20080307000058/http://tfgbd.web1000.com/...
(My goal is to get more software available on x86 CE because it just isn’t fun )
Thank you, I’ll work on adding your dll to the SCL. |
|
|
|
Factorite (Senior) Posts: | 84 |
Location: | Japan | Status: | |
| What I did is:
- Open the .vcw workspace on eVC4
- Go to "Build -> Configulation" and click "Add"
- Select "Win32 (WCE x86)" for CPU
- Select "*Default Release Configuration" for the configuration to copy from
- Keep the configuration name, which should become "Release"
- Change the target to this newly created configuration and build
- Done
Since there may some settings that are not compatible between CPUs, I selected the default and was going to tweak if evc4 complains (this can be hard, though ). Fortunately, it didn't require any further tweaks. |
|
|
|
Subscribers H/PC Guru Posts: | 5,661 |
Location: | United States | Status: | |
| Thank you for the explanation. That’s how I was doing it too and was only successful in the first page of this thread list entries (thenzero and I dunk for bananas contributed too)
I was having better luck lately because I figured out I can copy some of the header files that are missing from the other directories and that reduces my error count but I still get stuck with those linker errors)
I need to see if there’s anymore easy programs to compile. I want to try PocketPutty next |
|
|
|
Factorite (Senior) Posts: | 84 |
Location: | Japan | Status: | |
| Hmm, not sure but might be a file encoding issue. That source uses Japanese characters in comments and Japanese UI strings and they are encoded in Shift_JIS, which is the only way to support Japanese language in eVC4, but its not compatible with ASCII and often causes problems for non-Japanese software (and yes I use Japanese version of eVC4). In that case, you might have some luck by converting all files from Shift_JIS to UTF-8. This breaks Japanese strings but at least makes them not "harmful" for non-Japanese software. |
|
|
|
Subscribers H/PC Guru Posts: | 5,661 |
Location: | United States | Status: | |
| Ohhh! Okay that makes sense
So theoretically if I setup a build system using Windows 2000 JP, I may have better luck just "easy compiling"?
If so I think that’s worth doing !! |
|
|