Re: [Intel-gfx] [IGT PATCH] README: list some of the dependencies

2013-10-16 Thread Ben Widawsky
On Tue, Oct 08, 2013 at 09:19:06PM +0300, Jani Nikula wrote:
 Signed-off-by: Jani Nikula jani.nik...@intel.com
 ---
  README |   12 
  1 file changed, 12 insertions(+)
 
 diff --git a/README b/README
 index 653bfcd..a04c987 100644
 --- a/README
 +++ b/README
 @@ -96,3 +96,15 @@ debugger/
   initiating connections with debug clients..
  
   The debugger must be run as root: sudo debugger/eudb
 +
 +DEPENDENCIES
 + This is a non-exchaustive list of package dependencies required for
 + building everything:
 +
 + libpciaccess-dev
 + libdrm-dev
 + xutils-dev
 + libcairo2-dev
 + swig2.0
 + libpython3.3-dev
 + x11proto-dri2-dev

I've pushed this. Some documentation is better than no documentation.

-- 
Ben Widawsky, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [IGT PATCH] README: list some of the dependencies

2013-10-09 Thread Jani Nikula
On Wed, 09 Oct 2013, Ben Widawsky b...@bwidawsk.net wrote:
 On Tue, Oct 08, 2013 at 09:19:06PM +0300, Jani Nikula wrote:
 Signed-off-by: Jani Nikula jani.nik...@intel.com
 ---
  README |   12 
  1 file changed, 12 insertions(+)
 
 diff --git a/README b/README
 index 653bfcd..a04c987 100644
 --- a/README
 +++ b/README
 @@ -96,3 +96,15 @@ debugger/
  initiating connections with debug clients..
  
  The debugger must be run as root: sudo debugger/eudb
 +
 +DEPENDENCIES
 +This is a non-exchaustive list of package dependencies required for
 +building everything:
 +
 +libpciaccess-dev
 +libdrm-dev
 +xutils-dev
 +libcairo2-dev
 +swig2.0
 +libpython3.3-dev
 +x11proto-dri2-dev

 I guess my gripe with this kind of thing is people always tend you use
 distro specific package names. Can we somehow prevent it though?

Another problem is that it's bound to get stale. I just listed all the
stuff I needed to install when I tried to build igt on a semi-fresh
debian based installation. My gripe is having to run ./autogen.sh N
times, trying to figure out which package would fix the errors each
time. If only there was an option to list the dependencies!

I'm fine with not merging this. If anyone has better ideas, patches
welcome. ;)

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [IGT PATCH] README: list some of the dependencies

2013-10-09 Thread Ben Widawsky
On Wed, Oct 09, 2013 at 10:09:32AM +0300, Jani Nikula wrote:
 On Wed, 09 Oct 2013, Ben Widawsky b...@bwidawsk.net wrote:
  On Tue, Oct 08, 2013 at 09:19:06PM +0300, Jani Nikula wrote:
  Signed-off-by: Jani Nikula jani.nik...@intel.com
  ---
   README |   12 
   1 file changed, 12 insertions(+)
  
  diff --git a/README b/README
  index 653bfcd..a04c987 100644
  --- a/README
  +++ b/README
  @@ -96,3 +96,15 @@ debugger/
 initiating connections with debug clients..
   
 The debugger must be run as root: sudo debugger/eudb
  +
  +DEPENDENCIES
  +  This is a non-exchaustive list of package dependencies required for
  +  building everything:
  +
  +  libpciaccess-dev
  +  libdrm-dev
  +  xutils-dev
  +  libcairo2-dev
  +  swig2.0
  +  libpython3.3-dev
  +  x11proto-dri2-dev
 
  I guess my gripe with this kind of thing is people always tend you use
  distro specific package names. Can we somehow prevent it though?
 
 Another problem is that it's bound to get stale. I just listed all the
 stuff I needed to install when I tried to build igt on a semi-fresh
 debian based installation. My gripe is having to run ./autogen.sh N
 times, trying to figure out which package would fix the errors each
 time. If only there was an option to list the dependencies!
 
 I'm fine with not merging this. If anyone has better ideas, patches
 welcome. ;)
 
 BR,
 Jani.
 
 

I think it's better than nothing... just wanted to see if anyone had
better ideas. I just use the wrong package manager, I suppose. It is
definitely irritating that autofoo can't just create the list for us.

Also, a few of the deps you list are optional (though I think it makes
sense to do what you did, which is a default build).


-- 
Ben Widawsky, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [IGT PATCH] README: list some of the dependencies

2013-10-08 Thread Ben Widawsky
On Tue, Oct 08, 2013 at 09:19:06PM +0300, Jani Nikula wrote:
 Signed-off-by: Jani Nikula jani.nik...@intel.com
 ---
  README |   12 
  1 file changed, 12 insertions(+)
 
 diff --git a/README b/README
 index 653bfcd..a04c987 100644
 --- a/README
 +++ b/README
 @@ -96,3 +96,15 @@ debugger/
   initiating connections with debug clients..
  
   The debugger must be run as root: sudo debugger/eudb
 +
 +DEPENDENCIES
 + This is a non-exchaustive list of package dependencies required for
 + building everything:
 +
 + libpciaccess-dev
 + libdrm-dev
 + xutils-dev
 + libcairo2-dev
 + swig2.0
 + libpython3.3-dev
 + x11proto-dri2-dev

I guess my gripe with this kind of thing is people always tend you use
distro specific package names. Can we somehow prevent it though?

$ sudo pacman -S libpciaccess-dev
error: target not found: libpciaccess-dev

-- 
Ben Widawsky, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [IGT PATCH] README: list some of the dependencies

2013-10-08 Thread Anca Emanuel
I'm using Ubuntu 13.10

sudo apt-get install libpciaccess-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  libpciaccess-dev
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 23,6 kB of archives.
After this operation, 121 kB of additional disk space will be used.
Get:1 http://ro.archive.ubuntu.com/ubuntu/ saucy/main libpciaccess-dev
amd64 0.13.2-1 [23,6 kB]
Fetched 23,6 kB in 0s (160 kB/s)
Selecting previously unselected package libpciaccess-dev:amd64.
(Reading database ... 232755 files and directories currently installed.)
Unpacking libpciaccess-dev:amd64 (from
.../libpciaccess-dev_0.13.2-1_amd64.deb) ...
Setting up libpciaccess-dev:amd64 (0.13.2-1) ...


Hmm. You need to discuss this with your dristro maintainers.

On Wed, Oct 9, 2013 at 2:11 AM, Ben Widawsky b...@bwidawsk.net wrote:
 On Tue, Oct 08, 2013 at 09:19:06PM +0300, Jani Nikula wrote:
 Signed-off-by: Jani Nikula jani.nik...@intel.com
 ---
  README |   12 
  1 file changed, 12 insertions(+)

 diff --git a/README b/README
 index 653bfcd..a04c987 100644
 --- a/README
 +++ b/README
 @@ -96,3 +96,15 @@ debugger/
   initiating connections with debug clients..

   The debugger must be run as root: sudo debugger/eudb
 +
 +DEPENDENCIES
 + This is a non-exchaustive list of package dependencies required for
 + building everything:
 +
 + libpciaccess-dev
 + libdrm-dev
 + xutils-dev
 + libcairo2-dev
 + swig2.0
 + libpython3.3-dev
 + x11proto-dri2-dev

 I guess my gripe with this kind of thing is people always tend you use
 distro specific package names. Can we somehow prevent it though?

 $ sudo pacman -S libpciaccess-dev
 error: target not found: libpciaccess-dev

 --
 Ben Widawsky, Intel Open Source Technology Center
 ___
 Intel-gfx mailing list
 Intel-gfx@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/intel-gfx
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx