From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6818] New: toolchainfile.cmake has absolut path references
Date: Fri, 31 Jan 2014 15:31:38 +0000 (UTC) [thread overview]
Message-ID: <bug-6818-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6818
Summary: toolchainfile.cmake has absolut path references
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: u.strempel at googlemail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
On build process of buildroot the toolchainfile.cmake is created, but with
wrong absolut path.
When shareing the toolchain or move the folder you get problems this path
settings.
i.e.
set(CMAKE_C_COMPILER
/home/dev/Buildroot/../Toolchain/arm-toolchain//usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc)
set(CMAKE_CXX_COMPILER
/home/dev/Buildroot/../Toolchain/arm-toolchain//usr/bin/arm-buildroot-linux-uclibcgnueabi-g++)
A workarround for cmake files is
- get the path of the toolchainfile.cmake
And set the the variables.
get_filename_component(CMAKE_TOOLCHAIN_PATH ${CMAKE_CURRENT_LIST_FILE} PATH)
set(CMAKE_C_COMPILER
${CMAKE_TOOLCHAIN_PATH}/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc)
set(CMAKE_CXX_COMPILER
${CMAKE_TOOLCHAIN_PATH}/usr/bin/arm-buildroot-linux-uclibcgnueabi-g++)
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-01-31 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 15:31 bugzilla at busybox.net [this message]
2014-02-01 8:39 ` [Buildroot] [Bug 6818] toolchainfile.cmake has absolut path references bugzilla at busybox.net
2014-02-01 11:27 ` bugzilla at busybox.net
2014-02-07 8:36 ` bugzilla at busybox.net
2014-02-13 14:56 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-6818-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox