From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 1] Disable check for C++ compiler
Date: Sun, 14 Oct 2012 11:35:38 +0200 [thread overview]
Message-ID: <e33fa7a0d77ca247f73d.1350207338@skate> (raw)
In-Reply-To: <patchbomb.1350207337@skate>
# HG changeset patch
# User Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
# Date 1350206855 -7200
# Node ID e33fa7a0d77ca247f73db7f36722261319521951
# Parent 6f2b87c8b1f3bf88e9d0a75191e4f8efb1bcc791
Disable check for C++ compiler
By default, CMake assumes that a project uses both the C and C++
languages, and unionfs-fuse's CMakeLists.txt doesn't explicit which
languages it uses. Therefore CMake checks for both a C compiler and a
C++ compiler, which prevents from building unionfs-fuse on platforms
that don't have a C++ compiler.
We adjust unionfs-fuse CMakeLists.txt to explicity state that we only
use the C language, so that the C++ compiler check is no longer
performed by Cmake.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
diff -r 6f2b87c8b1f3 -r e33fa7a0d77c CMakeLists.txt
--- a/CMakeLists.txt Wed Sep 26 15:55:52 2012 +0200
+++ b/CMakeLists.txt Sun Oct 14 11:27:35 2012 +0200
@@ -1,4 +1,4 @@
-project(unionfs-fuse)
+project(unionfs-fuse C)
cmake_minimum_required(VERSION 2.0)
INCLUDE (CheckIncludeFiles)
prev parent reply other threads:[~2012-10-14 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 9:35 [Buildroot] [PATCH 0 of 1] Minor fix to CMakeLists.txt to disable C++ compiler check Thomas Petazzoni
2012-10-14 9:35 ` Thomas Petazzoni [this message]
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=e33fa7a0d77ca247f73d.1350207338@skate \
--to=thomas.petazzoni@free-electrons.com \
--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