Bug 1672067 - BUILDSTDERR: CMake Error: No source or binary directory provided
Summary: BUILDSTDERR: CMake Error: No source or binary directory provided
Keywords:
Status: CLOSED DUPLICATE of bug 1667306
Alias: None
Product: Fedora
Classification: Fedora
Component: cmake
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-03 13:51 UTC by Gerald Cox
Modified: 2019-02-03 14:57 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-03 14:57:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gerald Cox 2019-02-03 13:51:10 UTC
Description of problem:  When building copyq for F30 (and when releng also did for the mass rebuild) - fails with BUILDSTDERR: CMake Error: No source or binary directory provided.  Previously cmake for F29 and previous worked fine with no issues.

Apparently, the end of the cmake statement now REQUIRES a "space period", i.e. " ." to indicate directory.  I luckily was able to find this referenced in rhbz#1667306

Creating this record mainly so it's easier to find for others that are now sure to encounter this error.

Comment 1 Antonio T. (sagitter) 2019-02-03 13:57:38 UTC
>Apparently, the end of the cmake statement now REQUIRES a "space period", i.e. " ." to indicate directory.  I luckily was able to find this referenced in rhbz#1667306

Otherwise you can build in a dedicated "build" directory.

Comment 2 Gerald Cox 2019-02-03 14:07:56 UTC
(In reply to Antonio Trande from comment #1)
> >Apparently, the end of the cmake statement now REQUIRES a "space period", i.e. " ." to indicate directory.  I luckily was able to find this referenced in rhbz#1667306
> 
> Otherwise you can build in a dedicated "build" directory.

What are the advantages / disadvantages of using a dedicated "build" directory over just using the " ."

*** This bug has been marked as a duplicate of bug 1667306 ***

Comment 3 Gerald Cox 2019-02-03 14:57:33 UTC

*** This bug has been marked as a duplicate of bug 1667306 ***


Note You need to log in before you can comment on or make changes to this bug.