Am Freitag, 16. September 2016, 22:13:14 schrieb Gunter, Walter E:
> So, now that I am rocking and rolling using the correct toolchain, I am
> stuck with a failed compile.
> error: 'PF_CAN' was not declared in this scope
>
> Does this mean it can’t find the header file? I am just implementing
Okay…that made a huge difference.
Just moving those set commands to a separate toolchain.cmake file worked. Even
though the commands were the same, and I had the CMAKE_FIND_ROOT_PATH at the
top of the toplevel CMakeLists.txt before project:
# where is the target environment
I am referencing some includes that are part of my embedded device toolchain,
#include
If I have setup the cross compile directory correctly, does it know about these
or do I need to make it known?
if so, what’ the best approach?
Current Main CMakeLists.txt
cmake_minimum_required(VERSION
So, now that I am rocking and rolling using the correct toolchain, I am stuck
with a failed compile.
error: 'PF_CAN' was not declared in this scope
Does this mean it can’t find the header file? I am just implementing the CAN
interface; nothing complex.
Here is my file…
Mycan.c
#include
Gunter, Walter E wrote:
> I am having some troubles getting cmake setup and wonder if cmake is the
> right tool.
> Thoughts? Suggestions?
Yes, it is. I do it basically every day. Read my advise and properly set up a
toolchain file, that is very likely the missing magic.
I setup the Main CMakeLists.txt to cross_compile using an arm toolchain:
cmake_minimum_required(VERSION 3.2)
project(enterprise CXX)
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_CXX_COMPILER
/opt/toolchains/arm-2008q3/bin/arm-none-linux-gnueabi-g++)
set(CMAKE_SYSTEM_PROCESSOR arm)
set(CMAKE_AR
Ah..got ya.
There are two in my toolchain:
Sys/socket.h
Linux/socket.h
I couldn't find AF_CAN or PF_CAN defined in the sys one, but it is in the linux.
I included it, but still getting the error when building that it can't find it.
-Original Message-
From: Rolf Eike Beer
Okay, so temporarily, to get it to compile, I did this in my mycan.c
#ifndef PF_CAN
#define PF_CAN 29
#endif
#ifndef AF_CAN
#define AF_CAN PF_CAN
#endit
Doesn't seem ideal, but I tried it. I got past that part, and now on to
something I have seen before:
[ 68%] Linking CXX executable
Hi Walter,
The dash before levent looks different from the ones before lrt and
lpthread. Are you sure it's not some kind of Unicode character?
Cheers,
Marcel Loose.
On 15/09/16 18:56, Gunter, Walter E wrote:
>
> I am cross-compiling for an arm, and can run cmake successfully, but
> when I run
I am having some troubles getting cmake setup and wonder if cmake is the right
tool.
Thoughts? Suggestions?
Walter E. Gunter, Jr.
Mechatronics Engineer/Roboticist
AGV R
Dematic North America
265 S 5200 W
Salt Lake City, UT 84104
801.715.2602
Customer Service 1.800.530.9153
DEMATIC l We
Gunter, Walter E wrote:
> I setup the Main CMakeLists.txt to cross_compile using an arm toolchain:
>
> cmake_minimum_required(VERSION 3.2)
>
> project(enterprise CXX)
>
> set(CMAKE_SYSTEM_NAME Linux)
> set(CMAKE_CXX_COMPILER
> /opt/toolchains/arm-2008q3/bin/arm-none-linux-gnueabi-g++)
>
Hi,
in [1] some pointed out that cmake seems to have a notion of _default
genrator_, that is: If you invoke cmake without the -D option, it chose a
generator depending on the platform and create the build scripts.
Is this nice feature officially supported by cmake? I could not find it
Okay. I made some changes to my cmake and am getting different errors, but
still make me think I am not cross compiling:
Should those be my cross compile toolchain instead of /usr/bin/c++ ??
-- The CXX compiler identification is GNU 5.4.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check
Hi Brad,
> For `cmake --build` we already need to detect the generator used
> for the build tree in order to ask it to construct the appropriate
> command line. For the VS generator we could directly run the same
> check that ZERO_CHECK would run in order to decide whether to regen
> the build
I can't commit to the gitlab , it says something regarding no disk space.
$ git push
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 2.36 KiB | 0 bytes/s, done.
Total 5 (delta 4), reused 0 (delta 0)
remote:
Thank you Brad. I took the aggressive way and completely wiped the environment
inside the debugged process. For those anyone wishing to do something similar,
here’s what I’ve done:
I wrote a PowerShell oneliner:
gci Env: | foreach { $_.Name + "=" + $_.Value } | Out-File -FilePath
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 7a2e9e8cb77e7ceeb7a160c8e83ed974c3db10b2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via a1d30dcccfa79e3f79ab13c88749a8d0f04f14aa (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via df4c1374fb8c4e1a966fc3610c4af0fc13d05fd5 (commit)
via
_VERSION_MINOR 6)
-set(CMake_VERSION_PATCH 20160916)
+set(CMake_VERSION_PATCH 20160917)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 48c68b9b5e6a1be92dcaaab66a53d11643ecb7b2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 4356bd7fe382585e59033287dcc43386689e5dc2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 60ebd0acf843bbe87f94b39d6807a072532cdb07 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 56f7811ded77e0bed029b0232655ed4d4f4971d5 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via fcbed9bc37a32ad48dbf6839d020c55cc749310b (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 38a378e10d93740c11ac713c6035e26d6838ad96 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 3efb3c0012a05ce1f19c99fb27b835c3ec057270 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 00fd64d1263901f96935e15c8d90ee8a338cee1a (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 554655bfd91450e7e4e7feb9bd3a383d769a5528 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 6f1b80bec03fbe19e3d8f56fdee84a8ca6e4fe93 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via cf0e005202b3d17ad1f3c17536065c5589b97f93 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 01ee277892e7846f2998f8101d4ea40596dcdc26 (commit)
via
On 09/16/2016 06:32 AM, csiga.b...@aol.com wrote:
> Now it’s only up to me to understand the entire process of Makefile
> generation.
> Global/Local Generators, LocalMakeFileGenerator3 (does 3 correspond to the
> third layer of makefiles? If yes, where is 2?)
The 3 is the third generation of
On 09/16/2016 03:37 AM, Yves Frederix wrote:
> This would work, but it would make all builds using 'cmake --build'
> more verbose as before actually starting the msbuild-build, this would
> always print an often large number of lines like:
>
> CMake does not need to re-run because
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 90c30da30240895a3cf717c7248b84f485771194 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via a6b04580f92ba926fac8b8feb401413824ee82d2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via b9ddf9801cb6b481ed076aa63b7dc8e619633115 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via f5db532193c0e1396286ba4bb796f4be38e3a420 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 5991d310b7b631ab0716bfb9e182260fe836bd60 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via f9224eb7b28c6c6456524906103e7f26b5afe17e (commit)
via
40 matches
Mail list logo
