UGENE Forum - Gentoo ebuild and questions about building from source

May 1^st, 2024 at 5:49am

Choose Language:

	Welcome, Guest. Please Login or Register
	Welcome to our forum.

Home

Help

UGENE Forum › General Category › Help and How-to › Gentoo ebuild and questions about building from source

‹ Previous Topic | Next Topic ›

Pages: 1

Gentoo ebuild and questions about building from source (Read 11553 times)

May 23^rd, 2010 at 11:04pm

Eugene Shatsky Offline
YaBB Newbies

Posts: 2

I've decided to write a Gentoo ebuild for UGENE.
A few questions:
-is CONFIG+=x64 qmake option for amd64 CPUs only, or for all 64-bit (that have "lm" in /proc/cpuinfo "flags" string)?
-have I understood correctly, CellBE/CUDA/AMD Stream aren't autodetected, so I have write proper checks followed with sedding ugene_globals.pri?
It would probably be a good idea to make it possible disabling certain plugins and translations via useflags.

IP Logged

Reply #1 - May 24^th, 2010 at 7:31pm

Mikhail Fursov Offline
YaBB Administrator

Gender:
Posts: 162

Hi!

Eugene Shatsky wrote on May 23^rd, 2010 at 11:04pm:

-is CONFIG+=x64 qmake option for amd64 CPUs only, or for all 64-bit (that have "lm" in /proc/cpuinfo "flags" string)?

We use it only for x86_64 platform

Eugene Shatsky wrote on May 23^rd, 2010 at 11:04pm:

-have I understood correctly, CellBE/CUDA/AMD Stream aren't autodetected, so I have write proper checks followed with sedding ugene_globals.pri?

Yes, user should point environment variables to CUDA or ATI SDKs before building UGENE.

Eugene Shatsky wrote on May 23^rd, 2010 at 11:04pm:

It would probably be a good idea to make it possible disabling certain plugins and translations via useflags.

Really good idea! Thanks for the feedback. We will plan adding this feature to one of the nearest versions.

---
UGENE team

IP Logged

Reply #2 - May 25^th, 2010 at 12:21am

Eugene Shatsky Offline
YaBB Newbies

Posts: 2

I don't have CUDA-compliant hardware, so I can't test what I'm writing for its support, I'll ask Gentoo Bugzilla members about it after posting my ebuild there when it will be clean enough...
Currently nvidia-cuda-toolkit is available through Portage, and its ebuild seems to create a file /etc/env.d/99cuda containing:
Code:

PATH=/opt/cuda/bin
ROOTPATH=/opt/cuda/bin
LDPATH=/opt/cuda/lib
MANPATH=/opt/cuda/man

It is then used by init scripts. PATH is added to users' PATH vars, and LDPATH is used to populate /etc/ld.so.conf.
But in ugene_globals.pri I see:
Code:

UGENE_CUDA_LIB_DIR = $$(CUDA_LIB_PATH)
UGENE_CUDA_INC_DIR = $$(CUDA_INC_PATH)

So these 2 vars are still needed, but during build-time only, while CUDA_BIN_PATH and LD_LIBRARY_PATH aren't at all, right?

IP Logged

Reply #3 - May 27^th, 2010 at 4:03pm

Ivan Efremov Offline
YaBB Administrator
Novosibirsk

Gender:
Posts: 46

Hi Eugene!
Definitely, these variables are needed during build-time only. They must be set in order to build ugene with CUDA support.

UGENE team

IP Logged

Reply #4 - Aug 27^th, 2010 at 6:47pm

Myckel Habets Offline
YaBB Newbies

Posts: 13

@Eugene, how is this ebuild progressing? Do you have it somewhere on a repository?

IP Logged

Reply #5 - Aug 9^th, 2011 at 2:40am

Aleksandr Offline
YaBB Newbies

Posts: 4

Code:

# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

EAPI=3

inherit qt4-r2

DESCRIPTION="free cross-platform genome analysis suite"
HOMEPAGE="http://ugene.unipro.ru/"
SRC_URI="http://${PN}.unipro.ru/downloads/${P}.tar.gz"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE="cuda sse2"

DEPEND="x11-libs/qt-gui:4
	  cuda? ( dev-util/nvidia-cuda-sdk )"
	  RDEPEND="${DEPEND}"

src_configure() {
    eqmake4 INSTALL_LIBDIR="/usr/$(get_libdir)" CONFIG+="x64" -r
}

src_install() {
    make INSTALL_ROOT="${D}" install || die "emake install failed"
    #cp -pPR src/_release/plugins/lib* "${D}/usr/$(get_libdir)/${PN}/plugins/"
}

IP Logged

Reply #6 - Oct 24^th, 2012 at 3:28am

Bela Offline
YaBB Newbies

Posts: 1

Thanks for the ebuild! Cheesy

Works for me on amd64.

I added it to my layman overlay, so it’s easier to access (layman -a and3k-sunrise).

Best regards from Vienna,
Bela

IP Logged

Pages: 1

‹ Previous Topic | Next Topic ›

« Home

‹ Board

Top of this page