MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011137CMakeCMakepublic2010-08-17 05:412014-03-05 09:58
ReporterModestas Vainius 
Assigned ToBrad King 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
Platformi386OSDebian GNU//LinuxOS Version6.0 prerelease
Product VersionCMake-2-8 
Target VersionCMake 3.0Fixed in VersionCMake 3.0 
Summary0011137: Unable to parse CMakeLists.txt in UTF-8 with BOM encoding
DescriptionForwarded from http://bugs.debian.org/593327 [^]

--------------
CMake is unable to parse CMakeLists.txt in UTF-8 with Byte Order Mark
encoding.
Steps To ReproduceAn example:

CMakeLists.txt contents:
=============================
cmake_minimum_required(VERSION 2.6.0 FATAL_ERROR)

project(az)
set(VERSION_STRING "0.0")

include(ProcessAROCCAMProject)
add_aroccam_project(${PROJECT_SOURCE_DIR}/az.awp)

include_directories(src/${PROJECT_NAME})
file(GLOB_RECURSE project_sources ${PROJECT_SOURCE_DIR}/src/${PROJECT_NAME}/*.cpp)
set(src_files ${project_sources} ${init_source_file})

find_package(Aroccam REQUIRED camera timer xlib_qtviewer)
include(AroccamApplication)

target_link_libraries(${TARGET})
=============================

On the command line:
vadim(EFF-C001):~/Sources/qs$ file CMakeLists.txt
CMakeLists.txt: UTF-8 Unicode (with BOM) text
vadim(EFF-C001):~/Sources/qs$ cd build
vadim(EFF-C001):~/Sources/qs/build$ cmake ..
CMake Error: Error in cmake code at
/home/vadim/Sources/qs/CMakeLists.txt:1:
Parse error. Expected a command name, got unquoted argument with text "cmake_minimum_required".
-- Configuring incomplete, errors occurred!
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-08-17 05:41Modestas VainiusNew Issue
2012-08-11 21:35David ColeStatusnew => backlog
2012-08-11 21:35David ColeNote Added: 0030391
2012-08-12 15:34Christoph Anton MittererNote Added: 0030461
2012-08-13 11:00David ColeNote Added: 0030566
2013-10-21 09:03Brad KingNote Added: 0034182
2013-10-21 09:03Brad KingAssigned To => Brad King
2013-10-21 09:03Brad KingStatusbacklog => resolved
2013-10-21 09:03Brad KingResolutionopen => fixed
2013-10-21 09:03Brad KingFixed in Version => CMake 3.0
2013-10-21 09:03Brad KingTarget Version => CMake 3.0
2014-03-05 09:58Robert MaynardNote Added: 0035289
2014-03-05 09:58Robert MaynardStatusresolved => closed

Notes
(0030391)
David Cole   
2012-08-11 21:35   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0030461)
Christoph Anton Mitterer   
2012-08-12 15:34   
Is it really a good idea to basically close and forget any such bugs or feature requests which currently no one cares about, just to not longer see them as open?

I mean putting them up for discussion on the lists won't likely lead to find one implementig it,... and problems get forgotten and good ideas lost...
(0030566)
David Cole   
2012-08-13 11:00   
I didn't "close" it -- I sent it to the backlog, which is the pool of bugs that nobody is actively looking at, but which are still open for consideration for future fixing.

This is the purpose of the backlog category, to track things that we still want to fix eventually, but which nobody is currently working on.

It's not forgotten or lost... it's in the backlog and will be brought back again later when somebody is actively working on it.
(0034182)
Brad King   
2013-10-21 09:03   
Fixed:

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dbd93336 [^]
(0035289)
Robert Maynard   
2014-03-05 09:58   
Closing resolved issues that have not been updated in more than 4 months