8 Mar
2011
8 Mar
'11
7:09 p.m.
When I build the packages, my build script copies all of the source files from my svn
storage location on my hard drive to $TMP, which is located at /dev/shm (ram disk).
I do not build the packages in the svn source tree on the hard drive.
If you are saying that I cannot build the package from with the copied source files at
$TMP, then I need some tutoring how to modify the build scripts accordingly. The wiki
provides no such details.
The process I am using is the same one I used to successfully build all the packages under
automake.
Darrell
--- On Tue, 3/8/11, Serghei Amelian <serghei(a)thel.ro> wrote:
From: Serghei Amelian <serghei(a)thel.ro>
Subject: Re: [trinity-devel] kdebase FTBFS with cmake
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Tuesday, March 8, 2011, 12:47 PM
On Tuesday 08 March 2011 20:39:49
Darrell Anderson wrote:
All of my build scripts work in $TMP, outside the
source tree. :)
I see this:
cd /dev/shm/kdebase/kioslave/nfs && rpcgen -c -o
nfs_prot_xdr.c /dev/shm/kdebase/kioslave/nfs/nfs_prot.x
This meaning that CMAKE_SOURCE_DIR is
/dev/shm/kdebase/kioslave/nfs, which are
the same with CMAKE_BINARY_DIR, which is
/dev/shm/kdebase/kioslave/nfs as
well.
Are you sure that you're out-of-source? If yes, why
nfs_prot.x is in build
directory?
Still can't build.
Darrell
--
Serghei
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting