Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DosBox only #55

Open
madoar opened this issue Jan 4, 2019 · 10 comments
Open

DosBox only #55

madoar opened this issue Jan 4, 2019 · 10 comments

Comments

@madoar
Copy link

madoar commented Jan 4, 2019

@qparis is it possible to build only DosBox (without wine) using winebuild?

@qparis
Copy link
Member

qparis commented Jan 4, 2019

Theoritically, yes we can. However, it's starting to be a little weird to call it wine, isn't it?

@madoar
Copy link
Author

madoar commented Jan 4, 2019

Yes, but do we want to limit this tool only to wine?
The issue why I'm asking:
I have a dos application for which I would like to write a Phoenicis script, the issue is that I need dosbox.
Therefore it would be nice if we could also build DosBox.
In addition I think it would make for a nice second type of engine for Phoenicis.

@qparis
Copy link
Member

qparis commented Jan 4, 2019

You are correct.
Concerning your dos application, you have two possibilities:
1 - use a dos support wine build until we support another solution
2 - create a new engine

@madoar
Copy link
Author

madoar commented Jan 4, 2019

What exactly do you mean by 2?
When providing a new engine for Phoenicis we need to do two tasks:

  1. Providing the engine in a downloadable and executable form (e.g. as a binary)
  2. Providing an engine implementation in the Phoenicis script repository, which then makes use of the downloaded engine binary

I think I'm able to do task two (I never implemented an engine implementation for Phoenicis before), but I don't think I can do task one.

@qparis
Copy link
Member

qparis commented Jan 4, 2019

I can provide the task one, no problem

@qparis
Copy link
Member

qparis commented Jan 4, 2019

I was just saying that concerning your app, you may want to simply use wine dosbox_support

@madoar
Copy link
Author

madoar commented Jan 4, 2019

Yes I can do that for now.

The issue with using wine_dosbox_support in my case is, that it comes with all the wine "overhead" that isn't required.
Therefore I would prefer a dosbox engine without wine longterm.

@plata
Copy link
Contributor

plata commented Jan 4, 2019

You could already create the DOS engine and use wine_dosbox_support. Then, later on, you only switch the source. I'm pretty sure you will find some places in Phoenicis which must be changed (e.g. container info page).

@madoar
Copy link
Author

madoar commented Jan 4, 2019

@plata do you know if our engines tab would work with multiple kinds of engines, or would it throw some exception if we provide multiple engine types?

@plata
Copy link
Contributor

plata commented Jan 4, 2019

In theory it should simply show multiple categories but I don't know if that's really working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants