New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 882725 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 11
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Create a custom template to allow writing package deps inside target definitions for platform2 GN files.

Project Member Reported by oka@chromium.org, Sep 11

Issue description

Currently

pkg_config("foo_config") {
  pkg_deps = [ "bar" ]
}

static_library("foo") {
  config += [ "foo_config" ]
}

is a idiom to use "bar" package config in "foo". Allow writing it as

p2_static_library("foo") {
  pkg_deps = [ "bar" ]
}

introducing custom templates p2_*.

 
Labels: -OS-Mac OS-Chrome
Disclaimer: I'm not very familiar with GN.

Is it possible to keep using static_library? Having variants of every standard directives sounds not very great... If it's impossible, maybe we can contiunue defining pkg_config.

Comment 3 Deleted

We can't keep using static_library.
Unknown variables in a directive causes error. We can not post-process it.

Having variants for standard directive sounds not great, but seemingly is something common, e.g. v8_executable, v8_static_library.

How about to keep pkg_config thingy for now, and if it turns out to be too irritating, reopen this bug?
sgtm. Thanks for consideration.

Status: WontFix (was: Assigned)

Sign in to add a comment