Skip to content
This repository was archived by the owner on Jan 31, 2025. It is now read-only.

Commit 157edae

Browse files
author
Sean V Kelley
committed
config: Update project name
Signed-off-by: Sean V Kelley <[email protected]>
1 parent 55a9894 commit 157edae

File tree

4 files changed

+14
-14
lines changed

4 files changed

+14
-14
lines changed

NEWS

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
libva-intel-driver NEWS -- summary of changes. 2016-11-10
1+
intel-vaapi-driver NEWS -- summary of changes. 2016-11-10
22
Copyright (C) 2009-2016 Intel Corporation
33

44
Version 1.7.3 - 10.Nov.2016

README

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11

2-
libva-intel-driver
2+
intel-vaapi-driver
33
VA driver for Intel G45 & HD Graphics family
44

5-
Copyright (C) 2009-2016 Intel Corporation
5+
Copyright (C) 2009-2017 Intel Corporation
66

77

88
License
@@ -14,7 +14,7 @@ Please read the COPYING file available in this package.
1414
Overview
1515
--------
1616

17-
libva-intel-driver is the VA-API implementation for Intel G45 chipsets
17+
intel-vaapi-driver is the VA-API implementation for Intel G45 chipsets
1818
and Intel HD Graphics for Intel Core processor family.
1919

2020
Platform definitions:

TESTING

+9-9
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Overview
33
--------
44

5-
The libva-intel-driver uses the Google Test Framework (gtest) for testing the
5+
The intel-vaapi-driver uses the Google Test Framework (gtest) for testing the
66
driver. Documentation for gtest can be found in the test/gtest/doc/
77
subdirectory. The original, upstream gtest project can be found at
88
https://github.com/google/googletest.
@@ -20,16 +20,16 @@ Google Test Framework Integration
2020
---------------------------------
2121

2222
Google Test recommends it be custom compiled for each project that uses it.
23-
Therefore, the libva-intel-driver project tracks a subset copy of the Google
23+
Therefore, the intel-vaapi-driver project tracks a subset copy of the Google
2424
Test Framework source code at release 1.8.0 (initially) in a test/gtest/
25-
subdirectory of the project source tree. The libva-intel-driver copy of gtest
25+
subdirectory of the project source tree. The intel-vaapi-driver copy of gtest
2626
will only be updated to new upstream releases (or critical upstream fixes) of
2727
gtest, only if it is necessary. As of this writing, the last release (1.8.0)
2828
was August 2016, about three years after its previous release. Thus, there
29-
should be minimal need to update or maintain gtest within the intel-driver
29+
should be minimal need to update or maintain gtest within the intel-vaapi-driver
3030
project.
3131

32-
Libva-intel-driver tests or other project code should *not* be intermixed within
32+
Intel-vaapi-driver tests or other project code should *not* be intermixed within
3333
the test/gtest/ subdirectory. The test/gtest/ subdirectory should only contain
3434
source from the upstream Google Test project to make upgrades simpler.
3535

@@ -38,8 +38,8 @@ Building Google Test Framework Library
3838
--------------------------------------
3939

4040
The Google Test Framework is compiled as a convenience library (libgtest.la)
41-
within the libva-intel-driver source tree. The rules to build libgtest.la are
42-
maintained in a custom makefile in the libva-intel-driver project tree
41+
within the intel-vaapi-driver source tree. The rules to build libgtest.la are
42+
maintained in a custom makefile in the intel-vaapi-driver project tree
4343
(see test/Makefile.am). The libgtest.la library will be automatically compiled
4444
if the tests are enabled by configuration.
4545

@@ -61,7 +61,7 @@ single test/test_i965_drv_video executable. Hence...
6161
Writing Driver Tests
6262
--------------------
6363

64-
Libva-intel-driver tests are defined in the test/ subdirectory using the Google
64+
Intel-vaapi-driver tests are defined in the test/ subdirectory using the Google
6565
Test Framework. All driver tests that need a VADriverContextP, VADisplay and
6666
etc. should define a test fixture that inherits from the I965TestFixture class
6767
and then use the gtest test fixture macro (TEST_F) to define the test case. The
@@ -141,6 +141,6 @@ these options).
141141
Distribution
142142
------------
143143

144-
A libva-intel-driver source distribution is generated during `make dist` and
144+
An intel-vaapi-driver source distribution is generated during `make dist` and
145145
includes the necessary Google Test Framework source code and makefile rules
146146
along with the driver test source code.

configure.ac

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ m4_define([libdrm_version], [2.4.52])
1818

1919
AC_PREREQ([2.57])
2020
AC_INIT([intel_driver], [intel_driver_version], [[email protected]],
21-
[libva-intel-driver])
21+
[intel-vaapi-driver])
2222
AC_CONFIG_SRCDIR([Makefile.am])
2323
AM_INIT_AUTOMAKE([1.9 tar-ustar])
2424

0 commit comments

Comments
 (0)