On 1/16/2013 6:57 PM, Laszlo Papp wrote:
This is my latest toolchain file version:
http://quickgit.kde.org/?p=scratch%2Flpapp%2Fwikireader.git&a=blob&h=5c6c4dbda324a8285f99115c3de7d45e441d47ca&hb=f296afed1993d7c28edd5f9adcfd41465667d823&f=frontends%2Fblackberry%2Fcmake%2FToolchain-QNX-8.0.0.cmake
This is my latest toolchain file version:
http://quickgit.kde.org/?p=scratch%2Flpapp%2Fwikireader.git&a=blob&h=5c6c4dbda324a8285f99115c3de7d45e441d47ca&hb=f296afed1993d7c28edd5f9adcfd41465667d823&f=frontends%2Fblackberry%2Fcmake%2FToolchain-QNX-8.0.0.cmake
At least, it is clear now what I should a
Hi Bill!
This works: echo "int main() { return 0; }" > main.cpp && qcc
-Vgcc_ntoarmv7le main.cpp -l QtCore -L
/opt/bbndk/target_10_0_9_1673/qnx6/armle-v7/usr/lib/qt4/lib/ -o cmake-test
This does not work: echo "int main() { return 0; }" > main.cpp &&
ntoarmv7-g++ main.cpp -lQtCore
-L/opt/bbndk/ta
Hi,
On Wed, Jan 16, 2013 at 11:01 PM, wrote:
> The problem is that the script fails when using cmake 2.6. I want to know
> if this is expected or a bug ?
>
> I filed a bug report with Red-Hat 6, but they just decided to ignore it. See
> https://bugzilla.redhat.com/show_bug.cgi?id=896116
The problem is that the script fails when using cmake 2.6. I want to know
if this is expected or a bug ?
I filed a bug report with Red-Hat 6, but they just decided to ignore it. See
https://bugzilla.redhat.com/show_bug.cgi?id=896116
Perhaps someone knows a way around this problem ?
> On
On 1/16/2013 4:05 PM, Laszlo Papp wrote:
At least I cannot reproduce the crash with the following skeleton:
You should look at the compile/link lines. First I would look at the
link lines:
This is the qmake one:
qcc -Vgcc_ntoarmv7le -lang-c++
-Wl,-rpath-link,/home/taylor/Development/bbndk
At least I cannot reproduce the crash with the following skeleton:
cat ../../cmake-test/main.cpp
int main() {return 0;}
cat ../../cmake-test/CMakeLists.txt
add_executable(cmake-test main.cpp)
I am running out of the quick ideas soon. Anything else to try?
On Wed, Jan 16, 2013 at 2:12 PM, Laszlo
On Tuesday 15 January 2013, Brad Bell wrote:
> I am trying to build a project for Red-hat 6 which uses the following
> cmake version
> bradbell@gorst trash]$ cmake --version
> cmake version 2.6-patch 4
>
> While doing so I am having trouble with the ADD_CUSTOM_TARGET. To be
> specifc, af
On Tuesday 15 January 2013, Michael Jackson wrote:
> There are lots of different ways to do this. The following is an example of
> what *I* do. - In my CMakeLists.txt file I have this
> set(DREAM3DLib_BUILT_AS_DYNAMIC_LIB)
> IF (BUILD_SHARED_LIBS)
> set(DREAM3DLib_BUILT_AS_DYNAMIC_LIB 1)
>
Hello,
Thank you very much .
Cmake work now on window
Best regards
mparchet
De : Brett Delle Grazie [mailto:brett.dellegra...@gmail.com]
Envoyé : lundi 14 janvier 2013 14:42
À : Parchet Michaël
Cc : KDE on Windows; cmake@cmake.org
Objet : Re: [CMake] How to set the cmake varia
Interesting finding! It happened to PySide as well on this platform which
may help with proceeding:
http://www.engcorp.com/pipermail/blackberry-python/2013/16.html
On Wed, Jan 16, 2013 at 10:31 AM, Laszlo Papp wrote:
> I have just tried to add the following libraries to the linkage even if
>
Am 16.01.2013 14:01, schrieb Eric Noulard:
2013/1/16 Rolf Eike Beer :
Eric Noulard wrote:
and fill-in the form.
Then attach the zip file to your bug report.
You can even reply to this thread by simply giving the URL of
the bug in order to ease connecting the dots.
You can add yourself as "mo
2013/1/16 Rolf Eike Beer :
> Eric Noulard wrote:
>
>> and fill-in the form.
>> Then attach the zip file to your bug report.
>>
>> You can even reply to this thread by simply giving the URL of
>> the bug in order to ease connecting the dots.
>>
>> You can add yourself as "monitoring" the bug so that
Eric Noulard wrote:
and fill-in the form.
Then attach the zip file to your bug report.
You can even reply to this thread by simply giving the URL of
the bug in order to ease connecting the dots.
You can add yourself as "monitoring" the bug so that you'll get
follow-up from mantis.
You don't
2013/1/16 BILODEAU Andre :
> Hello
>
> I have finally the simplest setup which reproduces random BAD_COMMAND
> errors:
> - no compilations or produced binaries, justs tests
> - tests are called without arguments or set properties
>
> There are 20 tests, all of the form
> add_test (test_02 ${CMA
I have just tried to add the following libraries to the linkage even if
they seem unnecessary: -lz -lsocket -lm -lbps, but it is still crashing. :'(
I have also tried to save out the wikireader.core file of mine, and run
through an arm gdb on the host, but it did not provide too much information
s
On Wed, Jan 16, 2013 at 9:54 AM, Laszlo Papp wrote:
> Here you can find the build with qmake:
> http://paste.kde.org/~lpapp/648440/
>
Sorry, I sent a wrong link for that. This is the correct:
http://pastebin.com/h4HjDFzU
Here you can also find my cmake toolchain file:
http://quickgit.kde.org/?p
Hi all,
As I have a few days left for the submission of the limited edition device
program, I thought I would be asking for help to see if it is something
simple to fix with joint effort as I like cmake. :-)
Otherwise I may need to switch away from cmake, and it will also be a
showstopper to star
Le mardi 15 janvier 2013 à 11:56 -0500, Michael Jackson a écrit :
>
> On Jan 15, 2013, at 11:44 AM, Bogdan Cristea wrote:
>
> > Le mardi 15 janvier 2013 à 11:31 -0500, Michael Jackson a écrit :
> >> There are lots of different ways to do this. The following is an
> >> example of what *I* do.
> >>
2013/1/16 Ingolf Steinbach :
> However, during generation phase, cmake emits the following messages:
[...]
It turns out that these messages do no longer appear after completely
removing my build directory, so they seem to be caused by some
left-over files. Please ignore my previous post. Sorry for
20 matches
Mail list logo
