Replies: 2 comments
-
I'd try using Also be aware that a target outside the build tree (like |
Beta Was this translation helpful? Give feedback.
0 replies
-
Likely you'll have to key off on one flavor or another of command line
arguments to decide which Install() is actually run.
see: https://scons.org/doc/production/HTML/scons-user.html#chap-command-line
…On Fri, Mar 24, 2023 at 10:53 AM Mats Wichmann ***@***.***> wrote:
I'd try using env.Substfile for this. SCons is always going to be unhappy
in some form if you have more than one rule for a single target path.
Also be aware that a target outside the build tree (like /usr/share)
isn't going to be selected by default - this often comes as a surprise.
—
Reply to this email directly, view it on GitHub
<#4331 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAUCNFLLA7I7BGESOOZYATW5WYQDANCNFSM6AAAAAAWGF7ZGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Suppose I have 2 files,
variant1/foo.txt
andvariant2/foo.txt
. I'd like to have 2 different install targets that both install them to/usr/share/foo/foo.txt
so users could decide what variant they want to install. How would I achieve this?Adding 2 install targets with something like
don't seem to work even with 2 different envs
Copy()
ed from the same env, with the error that states "target and source lists must have same length."Beta Was this translation helpful? Give feedback.
All reactions