Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Jochen Schäfer

Pages: [1] 2 3 ... 13
Applications / Re: LIBC panic errors anyone?
« on: January 10, 2022, 09:14:26 am »
I noticed that problem while using lsusb.

Programming / Re: Autoconf and OS/2
« on: December 19, 2021, 01:40:36 pm »
Silvan wrote a comment on Github, which I couldn't read because Github is sometimes weird.
So, I also checked and discovered some changes, concerning line endings, I missed.
I haven't fixed all problems, yet, but I'm getting there.
Thanks Silvan for the hints.

Programming / Re: Autoconf and OS/2
« on: December 19, 2021, 09:25:27 am »
It appears to be a shell issue. When the system posix shell is Dash you get a broken makefile. setting it to bash fixed the issue.
Don't think, that's the case. I used dash for the BWW version, too. I only have the problem with the new merged version.

@Dave: Thanks for the pointer to this tool.
And the missing objects bothered me, too, but I couldn't locate where the problem is, yet. At least, I'm not alone in this.

Programming / Re: Autoconf and OS/2
« on: December 18, 2021, 08:47:39 pm »
Oh yes. I committed it commented because 2.0.14 removed it and I didn‘t know whether it is still needed. Remove the comments and sh Then you are good to go.

Programming / Re: Autoconf and OS/2
« on: December 18, 2021, 05:41:43 pm »
Well, has only LF and not CRLF in both versions.
As I said, I have no problems with the BWW version. With my merge, I get the problems. It's possible, that something is wrong with my installation.
When somebody can check, how the Makefile is created from my repo (, I would be grateful.

Programming / Autoconf and OS/2
« on: December 18, 2021, 09:43:43 am »
I'm getting on and off in problems with the generated files by autoconf.
My recent case is SDL2. I have cloned BWW's version and tried to upgrade it to mainstream SDL 2.0.14.
I did the merge on my iMac, because it was so much easier with an IDE.
Now, I see consistently the following problem with the generated Makefile:
Code: [Select]
/SDL_test_assert.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_assert.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_common.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_common.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_compare.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_compare.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_crc32.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_crc32.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_font.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_font.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_fuzzer.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_fuzzer.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_harness.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_harness.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_imageBlit.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_imageBlit.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_imageBlitBlend.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_imageBlitBlend.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_imageFace.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_imageFace.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_imagePrimitives.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_imagePrimitives.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_imagePrimitivesBlend.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_imagePrimitivesBlend.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_log.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_log.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_md5.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_md5.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_memory.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_memory.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@ /SDL_test_random.lo: D:/WORK/sdl2/SDL2-os2/src/test/SDL_test_random.c $(objects)/.created $(RUN_CMD_CC)$(LIBTOOL) --tag=CC --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -MMD -MT $@ -c $< -o $@
This is all on one line and $(objects) is missing before all compile targets, e.g. "/SDL_test_assert.lo:"
Now, when I checkout the commit before the merge commit on the machine without any other changes, I have no problem with the generated Makefile.
For me, it is clear, that line ends are not generated and $(objects) is not expanded.

My question: Does anyone has some pointers, where the problem lies?

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 13, 2021, 08:40:07 am »
So I had some success with the HIDAPI interface to SDL2. It seems like HIDAPI only supports some common game controller like Xbox or PS4 controllers, at least when used via libusb. I plugged in my PS4 controller via USB and it shows up on testjoystick.
I think, I will push the changes upstream, so that we have at least that support.

@Lars, I can do that. I have attached a build of hidapitester with the needed HIDAPI dll. hidapitester -h gives you the parameters. Cf Dave's post with the link to the Github page of hidapitester for more informations.

EDIT: The PS4 game controller works as joystick on PrBoom.

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 11, 2021, 07:04:58 pm »
I tried further analyze the write errors from hidtest:
1.) It tries to write a feature report with number 0x02. The call to libusb_control_transfer gives me a return value of -1 (Input/Output value).
2.) Later, it writes to the device. The call to libusb_control_transfer also gives me a return value of -1.

When I press button or turn the stick, the read data gives me different data values. So that works at least.

@Lars: If you want to compile hidapi yourself, I have forked hidapi and applied Dave's diff and committed them. You find my repo here:

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 10, 2021, 09:16:42 pm »
Thank you, that did the job.
I keep forgetting the emximp incantation all the time ;-)

Compiled HIDAPI. Now I see the usb path in the device summary, but the test still can't write to the joystick.
Because I have no experience with USB programming, I have to ask, whether this can happen with some USB devices or should it always be posible to send feature reports?

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 10, 2021, 08:17:32 pm »
You have to change the hardcoded device id for the hid_open call, so that it points to one of the connected devices.

But I cannot configure libusb, because it seems my system cannot link usbcalls.

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 10, 2021, 06:23:17 pm »

It's here:

but there is still work to do (something's not quite right when you end a process with Ctrl-C). Nonetheless, you might want to try it.
Thank you, I wil try it out.

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 10, 2021, 04:14:03 pm »
By now, I have finished work on libusb (hopefully). I'll ask BWW to create an updated RPM. You might want to try the updated version and see if that helps. Proper support of "libusb_get_port_numbers" is still a problem (what error message did you get when trying out hidapi ?)
Where do I get your version from to build it myself?

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 09, 2021, 12:01:20 pm »
We've always been missing a lot of the wide character functions, Bitwise has added most but hadn't added wcsdup(). Sylvan must have seen this thread and opened the above referenced issue about it, so slowly we're getting all of them.

To keep everyone informed: I just made a pull request for a wcsdup implementation.

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 08, 2021, 04:48:24 pm »
Hi Jochen

Have you posted the updated hidapi? Didn't see it attached to any of the posts at the moment, and might want to see if it can see my joystick.

No, it's part of SDL2, so I have to try understand the code and tinker around with it, first. Perhaps, the new libusb helps. We will see.

Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 08, 2021, 08:58:40 am »
lsusb shows the joystick, but SDL2 doesn‘t. Since I don’t use hidapi directly, it have no error message.

Did you compile it yourself or use the one I compiled? Anyways here's the last version I compiled, used a different wcsdup() based on and hacked to not use iconv(). Test program and diff included.
Edit: fix typo
No, I used the version included in SDL2 with your wcsdup implementation. I'm now trying to compile the included hidapi, and test with that.

EDIT: I used hidtest from your version, but it says it cannot open the device.

BTW: Why do we have a lot wcs function,but not wcsdup?

Pages: [1] 2 3 ... 13