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 4 ... 7
16
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 11, 2019, 07:12:36 pm »
Hi Andreas.

Big thanks for the Warpin scripts. I will test them.


Bye Jochen

17
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 10, 2019, 08:31:32 am »
I don't know anymore. Perhaps it was the DOSBOX configure script acting up.
In the end, it comes down to me wanting to produce the RPM packages for the dependencies, but not being able to.
I wanted to look into the SDL source package, anyway. Perhaps there I can unearth something.

18
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 09, 2019, 11:31:33 pm »
I find it the best method to avoid inclusion of these files. That applies also to libcn. If you want to support people who defer to use RPM/YUM, I see it as the only option to provide the required files in a separate package. (Steve Wendt did that for Mozilla versions.) With "package" I mean also "file". That means: create a special .wpi with these DLLs, but better keep them quite hidden to ensure people don't install them by mistake.

Dave has already described what the biggest problem for other apps may be. So, easiest is to just refer to the "yum install" command to install the prerequisites. What WarpIN can do, is to check for prerequisites and defer installation without it. Let's see, if I find time during the weekend to give examples and to add that to the Dosbox .wis script.
Very helpful remarks. Since 15 years, I on and off release some Warpin packages for DOSBOX. Nobody ever complained about how I package it or suggested how to do it better.
Thank you Andreas and Dave.

19
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 09, 2019, 11:24:11 pm »
How are you building Dosbox, GCC or OpenWatcom? And likewise with the SDL libraries?
GCC 4, SDL from RPM.
I have to built the SDL dependencies like Ogg, SDL_net statically. I'm not able to build DLLs from them.

20
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 09, 2019, 11:19:06 am »
1.) The DLLs are their own package and don't need to be installed. @Andreas, how can I switch the default state of a package. Honestly, 15 years ago, when starting porting and maintaining DOSBOX, somebody write me the Warpin scripts.

2.) @Dave: Good hint. I will try to insert that in the next release.

EDIT:
3.) I really would to also build an RPM version, but I can't even get the SDL extension to build, because dynamic build seems to be impossible.

I'm open to suggestion about how to make the package better and more reliable. I'm just not familiar with every OS/2 intricacy, as I'm only use it to build DOSBOX.

21
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 08, 2019, 11:14:18 pm »
Again, LIBCN works on most OS/2 versions, AFAIK. So DOSBOX will work with it.If I use LIBCN, I will include it.
So, please stop your crusade in this thread, because it's not approbiate in the case of DOSBOX.
Or, do you know breaking changes happening in LIBCN?

The problem with including any version of libc, including LIBCN is that in a year, after LIBCN has been updated, a user might download your package and downgrade LIBCN and break other packages that depend on new functionality.
Yes, but the DLLs are installed in DOSBOX's directory. DLL hell, I know, but at least nothing gets mixed up.


22
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 08, 2019, 03:13:22 pm »
Again, LIBCN works on most OS/2 versions, AFAIK. So DOSBOX will work with it.If I use LIBCN, I will include it.
So, please stop your crusade in this thread, because it's not approbiate in the case of DOSBOX.
Or, do you know breaking changes happening in LIBCN?

23
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 08, 2019, 10:23:05 am »
Hey guys.

Calm down. There is a reason, why I include all the necessary DLLs in the DOSBOX package.
That I once build a binary with a still experimental DLL was a slip.
Martin is helpfully pointing me to the new status of LIBCN.
What is not helpful is the bickering about the one true OS/2. You don't need RPM for DOSBOX.
BTW, if you get the newest LIBC from a non-RPM source and build against it, guess what, you are still needing LIBCN.

So, please stop it guys.

24
Programming / Re: What is needed for Node.js apps?
« on: May 07, 2019, 04:23:35 pm »
Hi

Just from a theoretical point of view, I want to know what would be needed to have Node.js stand alone apps to run on OS/2.

What are the framework, library set and/or runtimes that are needed to have node.js application like Riot.im , Butter Project (base for popcorn time) and others running as stand alone apps? I know that some node.js apps runs on Firefox on OS/2 like Riot.im, but I was wondering what is needed to have those running as stand alone.

This is just for my knowledge, don't think that I'm saying it is the #1 priority for us.

Regards
You would also need V8, the Javascript interpreter running. It has a lot of dependencies.

25
Applications / Re: Discussion about RPM/YUM and Libcn
« on: May 07, 2019, 04:21:40 pm »
I noticed today that "libcn0.dll" is available on the regular (non experimental) netlabs rpm repository. That means that regular users can now get that DLL.
Thank you. Albeit I dare to state that "regular" implies all brands of OS/2, and mainly installs without bleedin' RPM, so it's a bit of a stretch to imply that ArcaOS and perhaps eCS 2.x are representing what "regular" is.

I haven't seen a more regular *CN* RPM ZIP file so far, FWIW. ArcaOS will be regular for users of an English OS indeed, but that's a minority. Surely you aren't claiming that users of e.g. a Spanish version of OS/2 aren't "regular users"... :)
He never implied regular OS/2. He was speaking of the regular RPM repository.

26
Applications / Re: Using a scanner with hplip?
« on: April 29, 2019, 01:52:24 pm »
Yes, the "musical note", hex value 0d, shows clearly, it exists at the end of all the hplip.conf lines.
Removed using kon and saved modified file.

That's actually a form feed (FF) rather then line ending character. Always a good idea to look with a hex editor.
Actually, 0X0D = 13 is Carriage Return. Form Feed is 0X0C = 12.

27
Applications / Re: New DOSBOX build / new ports
« on: April 10, 2019, 11:27:49 am »
It gets better and better ;-)
Thank you very much, David.

28
Hardware / Re: T420 and Intel 5100 Wifi
« on: April 01, 2019, 04:03:27 pm »
No, the 5100 is not whitelisted on a T420 with a vanilla BIOS, that's why I added the patched BIOS requirement for the half-size slot.
Follow the link in the Thinkwiki. There you will find the correct BIOS with whitelisting turned off (and some other enhancements like RAM speed).

AFAIK, the full size slot is where normally the WWAN card would go. But I never had one, so I can't help you with the SIM location.

29
Hardware / Re: T420 and Intel 5100 Wifi
« on: April 01, 2019, 11:02:19 am »
I bought the 5100 used on eBay.
You can try to swap the 4965, but be prepared that the BIOS complains, if you install it in the half-size slot under the keyboard.
AFAIK, the full size slot doesn't get checked, but then again you are blocked from installing eg. an SSD.

30
Applications / Re: New DOSBOX build / new ports
« on: March 30, 2019, 08:53:29 am »
I made a new release with David's new icons. Thanks again, David.
We have a new feature:
Quote
New Drive type: overlay.

When active, this drive redirects new and changed files to a different location.
The files in the overlay and normal drive are merged on startup and kept up to date when the game changes something.
Files in the overlay are priotizedi, if they exists, above the normal files.
The drive will switch to an overlayed version of the file on the first write! (Not when opening the file in write-mode).
The overlay is capable of creating missing directories.

With the help of DBOVERLAY files, the drive keeps track of files that are present in the normal directory but deleted by the game.
All changes are preserved between sessions.

Current design principles/limitations/requirements:
1) All directories that can be used for saving, must exist already in the base before mounting. (they will be created by DOSBox if missing in the overlay)
2) All filenames inside the overlay directories are UPPERCASE and conform to the 8.3 standard except for the special DBOVERLAY files.
3) To keep point 1 valid at all times, support for creating/renaming/removing directories has been disabled.

Thanks for the help GOG.

Have fun

Pages: 1 [2] 3 4 ... 7