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

games-arcade/alex4: create recipe for Alex the Allegator 4. (WIP) #666

Merged
merged 1 commit into from Jul 22, 2016

Conversation

@fbrosson
Copy link
Member

fbrosson commented Jun 23, 2016

TODO: Check if it would be OK to also import the patches in:
http://data.gpo.zugaina.org/gamerlay/games-arcade/alex4/files/
and sync with alex4-1.1 in http://gpo.zugaina.org/games-arcade/alex4

Maybe we should use a (modified) rdef instead of the alex4_BeOS_src/alex4.rsrc in alex4_beos_src.zip, because when Alex4 is launched from command line we see this warning:

Signature in rsrc doesn't match constructor arg. (application/x-vnd.Allegro-Alex4, application/x-vnd.freelunchdesign-alex4)
@fbrosson fbrosson mentioned this pull request Jun 23, 2016
TODO: Check if it would be OK to also import the patches in:
http://data.gpo.zugaina.org/gamerlay/games-arcade/alex4/files/
and sync with alex4-1.1 in http://gpo.zugaina.org/games-arcade/alex4
@fbrosson
Copy link
Member Author

fbrosson commented Jun 23, 2016

I've just dropped the "beos" suffix in the name of the recipe to match the Gentoo naming conventions.

Does anyone have sound working with Alex4?

@Begasus
Copy link
Contributor

Begasus commented Jun 24, 2016

Thanks for taking over, I haven't been on Haiku for a while now (busy with
the dogs), I'll try to take a look at the new PR later this evening :)

2016-06-23 19:36 GMT+02:00 fbrosson notifications@github.com:

I've just dropped the "beos" suffix in the name of the recipe to match the
Gentoo naming conventions.

Does anyone have sound working with Alex4?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#666 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/APUDAnBTEj5wpjuzSHjWnFvxOO3nXjoxks5qOsQUgaJpZM4I9BW4
.

@fbrosson
Copy link
Member Author

fbrosson commented Jun 24, 2016

No problem ;-)

@Begasus
Copy link
Contributor

Begasus commented Jun 25, 2016

Same thing for Terminal here, maye an updated rdef would be better :) and no sound also ...
PS, it still remains in the Deskbar after closing

@Begasus
Copy link
Contributor

Begasus commented Jul 5, 2016

If allegro is not installed I get a "nothing provides lib:liballeg_x86>=4.4.2 needed by ..."
Maybe there is something not right for allegro? (also the same as I try to install the devel package for allegro if the lib isn't installed already - although both are available in the packages folder for haikuports)

@fbrosson
Copy link
Member Author

fbrosson commented Jul 5, 2016

Both allegro and alex4 build OK on x86_gcc2 primary arch. So it should not be asking for any lib:lib*_x86. If you have built on one primary arch (e.g. Haiku/x86), then switched to another arch (e.g. Haiku/x86_gcc2) to build for e.g. x86_gcc2 then you need to clean the work-* build dir before you build for that other primary arch.
haikuporter -c alex4 will get rid of the right work-* directory.

@Begasus
Copy link
Contributor

Begasus commented Jul 5, 2016

I know they build ok (allegro and alex - and in this case it was atanks which is x86), the haikuporter -c option I also know of (I usualy do this to net clutter the system to much with unnescecary files:) )
I just ment, if allegro is not installed and I try to install the devel file for allegro I'm getting the message that there is nothing providing allegro (be it x86_gcc2 or x86)

@fbrosson
Copy link
Member Author

fbrosson commented Jul 5, 2016

Sorry, I though you were having the error message about allegro while installing alex4. I could not guess you had built allegro_x86 and were trying to install atanks_x86 ;-)
BTW, I guess you have found, in the meanwhile, that you needed to install allegro_x86 before (or with) atank_x86.

@waddlesplash
Copy link
Member

waddlesplash commented Jul 22, 2016

Can this be merged?

@fbrosson
Copy link
Member Author

fbrosson commented Jul 22, 2016

The patches mentioned in the TODO part of the commit comment allow to save some prefs. I was willing to integrate them but it needs some time because we would need to patch a patch. That's not difficult but it needs some time because it's almost like solving a puzzle...
Since I currently don't have enough free time for that, I'm OK with merging the recipe like as is.
Should I make some changes in the commit message and/or the title of this PR?

@waddlesplash waddlesplash merged commit 87a3f50 into haikuports:master Jul 22, 2016
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@waddlesplash
Copy link
Member

waddlesplash commented Jul 22, 2016

Nah, that's OK.

@fbrosson fbrosson deleted the fbrosson:alex4 branch Jul 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.