il I would like to help out maintaining these modules. I
have been reading this list for a while, and been a happy CMake user for
several years now. It has saved me a lot of time, so I deceided it was
time I contributed some of it back.
With kind regards,
Micha Hergarden
signature.asc
Description
PM spec file.
+if("${_RPM_SPEC_HEADER}" MATCHES "REQUIRES_PRE" OR
"${_RPM_SPEC_HEADER}" MATCHES "REQUIRES_POST")
+ string(REPLACE "_" "(" _PACKAGE_HEADER_NAME
"${_PACKAGE_HEADER_NAME}")
+ set(_PACKAGE_HEADER_NAME
Hello Djou,
You will be better of asking this question on the 'cmake' mailing list
itself. That is geared towards cmake users. This list is for people
developing cmake itself.
Here is a cmake example to get you started:
project(DEMO)
cmake_minimum_required(VERSION 2.8)
add_executable(demo main.
:
4b989d5f158e5135bf543438af00b03db0102ade
My questions:
- I anyone else running into this?
- Is this new behaviour intended?
- If so, what must I change to my scripts to get my build working again?
- If not, what can I do to help resolve it?
Please let me know if more information is needed.
With kind regards,
Micha Hergarden
On 02/05/2014 10:15 AM, Stephen Kelly wrote:
> Micha Hergarden wrote:
>> I have checked out and build the most recent versions to figure out when
>> this phenomena is introduced, and have narrowed it down to the following
>> commit :
>> 4b989d5f158e5135bf543438af00b03db0
