XCA is a certificate management package that requires qt4 The current live tree has an ebuild for the latest version: 0.6.4 Prefix needs it too :-) I need to use qmake to generate a proper makefile on the OSX platform, no clue if this is "acceptable" ebuild coding. Please advise :-) Reproducible: Always
Created attachment 166069 [details] Ebuild for xca
Depends on http://bugs.gentoo.org/show_bug.cgi?id=238365 because you need a working qt4 environment
1) why did you comment out a patch? 2) why did you have to add a dobin call? Doesn't emake install handle that? 3) xca is supported upstream on macos. are you sure that you need a qmake -o Makefile call? seems hacky to me.
1) The patch deals with fixes to the makefile, since I'm generating a new one with qmake the patch does damage not good 2) Sadly no 3) Yup, but then it expects qt4 at the normal macosx places and as framework, I can't get it to build with the standard make-file. Maybe it's something stupid I'm overlooking. It compiles right up to the end and then ld complains about missing symbols for everything QT related. The readme/INSTALL in the source suggests running qmake to generate a makefile if you have issues in non-standard environments, that works, but still needs the ssl-patch to work. I'm using the software and can testify that it works with the current ebuild. But hey, I'm slowly getting to know prefix and the impact on build-envs if you have any good tips to solve the above, I'm all ears :-)
(In reply to comment #4) > 1) The patch deals with fixes to the makefile, since I'm generating a new one > with qmake the patch does damage not good Ok, but..what about the other arches? if this patch is needed on say, linux..then you cannot blindly comment it out. You will need to do something like !x86-macos? epatch ..blah > 2) Sadly no Probably because you generated a new makefile then? not a deal killer though. > 3) Yup, but then it expects qt4 at the normal macosx places and as framework, I > can't get it to build with the standard make-file. Maybe it's something stupid > I'm overlooking. It compiles right up to the end and then ld complains about > missing symbols for everything QT related. The readme/INSTALL in the source > suggests running qmake to generate a makefile if you have issues in > non-standard environments, that works, but still needs the ssl-patch to work. Ah, makes sense now. > > I'm using the software and can testify that it works with the current ebuild. > But hey, I'm slowly getting to know prefix and the impact on build-envs if you > have any good tips to solve the above, I'm all ears :-) Generally the only thing that we try to do is keep the diff list as small as possible. The only "bad thing" in your ebuild is unconditionally commenting out the patch - since I don't know anything about this package I can't really comment on it much more. I will test out a plain ecopy'd ebuild and see how that fares for me then look at your changes.
Oh boy. I was working on this some time ago and now I see grobian has been working on it as well. He appears to have made it work on osx from the commit message. Please test and re-open or file a new bug if something is wrong. Thanks for your work.
ah, shit, yeah. I needed it at work the other day, so I decided to fix the utterly broken "configure" script. I'm not sure what went wrong with the huge patching out here, it was just a linkage issue. Anyway, I successfully generated some keys with the tool, so it was/is working for me.
(In reply to comment #7) > ah, shit, yeah. I needed it at work the other day, so I decided to fix the > utterly broken "configure" script. *grin* since grobian recently started working where I work, that sorta explains the dual work :-) I'll sync my tree and have a look at his "configure" script patching
