VOGONS


DOSBox SVN Builds

Topic actions

Reply 20 of 294, by robertmo

User metadata
Rank l33t++
Rank
l33t++

EmuCR
These builds are updated not a few times a week but daily provided there was a change to dosbox's source. Although it fails to detect changes properly cause if the build was updated and there was a change or changes to dosbox's source that same day, no new build will be created until there is a change to the source some other day. So if there will be no source change for a month the build will not be updated to the latest source for a month too.

Reply 21 of 294, by HunterZ

User metadata
Rank l33t++
Rank
l33t++
robertmo wrote:

EmuCR
These builds are updated not a few times a week but daily provided there was a change to dosbox's source. Although it fails to detect changes properly cause if the build was updated and there was a change or changes to dosbox's source that same day, no new build will be created until there is a change to the source some other day. So if there will be no source change for a month the build will not be updated to the latest source for a month too.

I've noted this in the wiki. I'll try to email them and see if they know about the issue.

Reply 23 of 294, by Great Hierophant

User metadata
Rank l33t
Rank
l33t

I cannot get the latest EmuCR builds of the source to work. When DOSBox is run, it requests libpng12.dll, msvcp100.dll, & msvcr100.dll. When I find those files from the net and put them into the DOSBox directory where a straight 0.74 is installed, I get an Application Error, "unable to start correctly (0xc000007b). Click OK to close the application."

http://nerdlypleasures.blogspot.com/ - Nerdly Pleasures - My Retro Gaming, Computing & Tech Blog

Reply 25 of 294, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

You aren't trying to use the EMUCR build of DOSBox on an OS older than XP are you?

EmuCR builds requires Visual C++ 2010 which only works on XP+ (officially).

If you want to use Visual C++ 2010 on 2000 then you can try the blackwingcats ver: http://blog.livedoor.jp/blackwingcat/archives/1192179.html

but really stay away from the emucr DOSBox build if you are using a Windows OS older than XP. IIRC Qbix compiles the latest SVN but not sure if he wants it public or not. PM him and he'll probly give you the link.

How To Ask Questions The Smart Way
Make your games work offline

Reply 26 of 294, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

Someone ought to compile using mingw GCC so that there aren't goofy runtime DLL dependencies.

The VC++ DLL dependencies are even worse than what you get when compiling with cygwin GCC 😜

Reply 27 of 294, by Great Hierophant

User metadata
Rank l33t
Rank
l33t
HunterZ wrote:

Does ykhwong's build have those .dll's? His latest build is based on the same SVN version.

He has msvcp100.dll & msvcr100.dll but not libpng12.dll. However, when I copied his dlls into the folder, the SVN worked. libpng12.dll still needs to be acquired from another source.

http://nerdlypleasures.blogspot.com/ - Nerdly Pleasures - My Retro Gaming, Computing & Tech Blog

Reply 31 of 294, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

Feel free to add an entry for it on the wiki page! I can't access DOSBox-X's maintainer's web site to see what's there and get good links.

Also, it looks like EmuCR is doing vanilla SVN builds again.

Edit: Should probably refactor the builds lists into one or more tables as well.

Reply 33 of 294, by HunterZ

User metadata
Rank l33t++
Rank
l33t++
Serious Callers Only wrote:

Is 3708 the SVN version used? If not, is there a way to tell which version a given build is based on?

Reply 34 of 294, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

Updated the wiki.

I can't make sense of the DOSBox-X thread - the links are all over the place, and some of the newer links are to source code instead of binaries.

Reply 35 of 294, by Serious Callers Only

User metadata
Rank Member
Rank
Member
HunterZ wrote:
Serious Callers Only wrote:

Is 3708 the SVN version used? If not, is there a way to tell which version a given build is based on?

The last number comes from the svn revision. It should always be the last or near the last anyway, if launchpad does what it says it does.

edit: wait, wtf, no, it's really the last revision not that number... i think that the recipe is using the wrong substitution variable for the name (trunk really is the last dosbox commit, that danoon fix)

this is the recipe:
https://code.launchpad.net/~i30817/+recipe/dosbox-patched

# bzr-builder format 0.3 deb-version {debversion}+{revno}
lp:dosbox
merge packaging lp:~i30817/dosbox/packaging
nest munt lp:munt src/munt

Humm, i might be using the wrong original repository....
lp:dosbox might only mirror the official releases... gotta check.

Reply 36 of 294, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Edit nope:
https://code.launchpad.net/~mgiuca/dosbox/trunk
(this is lp:dosbox )
and last change:
3708. By qbix79 on 2012-09-25

Fix small oversight from revision 3666. Thanks for spotting this danoon

which seems right except for the number...
there are two revision number substitutions:
{revno} == 3708 apparently
and
{svn-revno} == maybe this is it?

Ok testing and will know in 10 minutes (i think the revno is the bazaar 'push' from the mirror sync and svn-revno should be the upstream svn revision), regardless, on the wiki you could just put in 'on the package name' (if i can make svn-revno work) since ideally that number will change.

Reply 37 of 294, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Ahah. A bug... the svn bazaar mirror doesn't want to work with {svn-revno}.

I think a date would be best then? Just to verify that the build is not 2 years old...

annoying.

Reply 38 of 294, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

you might be take in account that the svn location has changed a little while ago. So the lp mirror will be out of date.

Water flows down the stream
How to ask questions the smart way!

Reply 39 of 294, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Really? Was the last commit there
" Fix small oversight from revision 3666. Thanks for spotting this danoon "?
Because if so, it appears to be in the mirror.

edit:
lp:dosbox is using https://dosbox.svn.sourceforge.net/svnroot/do … ox/dosbox/trunk
which is more recent than what is in sourceforge
http://svn.code.sf.net/p/dosbox/code-0/dosbox/trunk dosbox-code-0

?