Qt-interest Archive, June 2007
qmake and cp command
Message 1 in thread
Makefiles generated by qmake have an illegal option for the command cp.
The option is --parents
What should this option do, exactly, allowing me to write a custom
file copier,
------
What is a woman that you forsake her, and the hearth fire and the
home acre,
to go with the old grey Widow Maker. --Kipling, harp song of the
Dane women
Tommy Nordgren
tommy.nordgren@xxxxxxxxx
--
[ signature omitted ]
Message 2 in thread
On 30.06.07 17:00:44, Tommy Nordgren wrote:
> Makefiles generated by qmake have an illegal option for the command cp.
Uhm, I rather think you've got the wrong cp at hand. At least the cp's
that I have around do know this option.
> The option is --parents
> What should this option do, exactly, allowing me to write a custom file copier,
man cp on a System that has a recent cp. What System and Qt are you
using? What version of cp?
Andreas
--
[ signature omitted ]
Message 3 in thread
On 30 jun 2007, at 18.45, Andreas Pakulat wrote:
> On 30.06.07 17:00:44, Tommy Nordgren wrote:
>> Makefiles generated by qmake have an illegal option for the
>> command cp.
>
> Uhm, I rather think you've got the wrong cp at hand. At least the cp's
> that I have around do know this option.
>
>> The option is --parents
>> What should this option do, exactly, allowing me to write a custom
>> file copier,
>
> man cp on a System that has a recent cp. What System and Qt are you
> using? What version of cp?
>
> Andreas
>
> --
> Be careful! Is it classified?
>
My System is Mac OS X 10.4.9 (Tiger), and I've downloaded the source
from Apple's developer web site.
Checking the code, confirms what reading the manpage indicates - that
there is no long options for cp on this system.
------------------------------------------------------
"Home is not where you are born, but where your heart finds peace" -
Tommy Nordgren, "The dying old crone"
tommy.nordgren@xxxxxxxxx
--
[ signature omitted ]
Message 4 in thread
Make sure you have the make-spec set correctly. Are you using XCode or
command-line builds? Which Qt version? (I am using 4.3 with a commercial-src
install.)
Digging into the qmake.conf files, I find:
QMAKE_COPY = cp -f
I did a grep on all the .conf files under mkspecs on Mac, and --parent did
not appear anywhere.
Keith
**Please do not reply to me, reply to the list.**
On 06-30-2007 12:30 PM, "Tommy Nordgren" wrote:
>
> On 30 jun 2007, at 18.45, Andreas Pakulat wrote:
>
>> On 30.06.07 17:00:44, Tommy Nordgren wrote:
>>> Makefiles generated by qmake have an illegal option for the
>>> command cp.
>>
>> Uhm, I rather think you've got the wrong cp at hand. At least the cp's
>> that I have around do know this option.
>>
>>> The option is --parents
>>> What should this option do, exactly, allowing me to write a custom
>>> file copier,
>>
>> man cp on a System that has a recent cp. What System and Qt are you
>> using? What version of cp?
>>
>> Andreas
>>
>> --
>> Be careful! Is it classified?
>>
> My System is Mac OS X 10.4.9 (Tiger), and I've downloaded the source
> from Apple's developer web site.
> Checking the code, confirms what reading the manpage indicates - that
> there is no long options for cp on this system.
>
> ------------------------------------------------------
> "Home is not where you are born, but where your heart finds peace" -
> Tommy Nordgren, "The dying old crone"
> tommy.nordgren@xxxxxxxxx
--
[ signature omitted ]
Message 5 in thread
On 30 jun 2007, at 19.46, Keith Esau wrote:
> Make sure you have the make-spec set correctly. Are you using XCode or
> command-line builds? Which Qt version? (I am using 4.3 with a
> commercial-src
> install.)
>
> Digging into the qmake.conf files, I find:
>
> QMAKE_COPY = cp -f
>
> I did a grep on all the .conf files under mkspecs on Mac, and --
> parent did
> not appear anywhere.
>
> Keith
> **Please do not reply to me, reply to the list.**
>
Of course not: The option is hardcoded in the C++ source for qmake.
------
What is a woman that you forsake her, and the hearth fire and the
home acre,
to go with the old grey Widow Maker. --Kipling, harp song of the
Dane women
Tommy Nordgren
tommy.nordgren@xxxxxxxxx
--
[ signature omitted ]
Message 6 in thread
If you look in the qmake source code, you'll see the unix makefile
generator inserts:
"$(COPY_FILE) --parents"
However, this shouldn't be a problem on a Mac platform. Make sure
your QMAKESPEC is set to either macx-g++ or macx-xcode.
Michael
On Jun 30, 2007, at 12:46 PM, Keith Esau wrote:
> Make sure you have the make-spec set correctly. Are you using XCode or
> command-line builds? Which Qt version? (I am using 4.3 with a
> commercial-src
> install.)
>
> Digging into the qmake.conf files, I find:
>
> QMAKE_COPY = cp -f
>
> I did a grep on all the .conf files under mkspecs on Mac, and --
> parent did
> not appear anywhere.
>
> Keith
> **Please do not reply to me, reply to the list.**
>
>
> On 06-30-2007 12:30 PM, "Tommy Nordgren" wrote:
>
>>
>> On 30 jun 2007, at 18.45, Andreas Pakulat wrote:
>>
>>> On 30.06.07 17:00:44, Tommy Nordgren wrote:
>>>> Makefiles generated by qmake have an illegal option for the
>>>> command cp.
>>>
>>> Uhm, I rather think you've got the wrong cp at hand. At least the
>>> cp's
>>> that I have around do know this option.
>>>
>>>> The option is --parents
>>>> What should this option do, exactly, allowing me to write a custom
>>>> file copier,
>>>
>>> man cp on a System that has a recent cp. What System and Qt are you
>>> using? What version of cp?
>>>
>>> Andreas
>>>
>>> --
>>> Be careful! Is it classified?
>>>
>> My System is Mac OS X 10.4.9 (Tiger), and I've downloaded the source
>> from Apple's developer web site.
>> Checking the code, confirms what reading the manpage indicates - that
>> there is no long options for cp on this system.
>>
>> ------------------------------------------------------
>> "Home is not where you are born, but where your heart finds peace" -
>> Tommy Nordgren, "The dying old crone"
>> tommy.nordgren@xxxxxxxxx
>
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
> with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
>
>
--
[ signature omitted ]
Message 7 in thread
That is an option I've never seen. Here is the man page from Mac OS 10.4.10
(about as recent as you can get, updated last week):
CP(1) BSD General Commands Manual
CP(1)
NAME
cp -- copy files
SYNOPSIS
cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] source_file target_file
cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] source_file ...
target_directory
Keith
**Please do not reply to me, reply to the list.**
On 06-30-2007 11:45 AM, "Andreas Pakulat" wrote:
> On 30.06.07 17:00:44, Tommy Nordgren wrote:
>> Makefiles generated by qmake have an illegal option for the command cp.
>
> Uhm, I rather think you've got the wrong cp at hand. At least the cp's
> that I have around do know this option.
>
>> The option is --parents
>> What should this option do, exactly, allowing me to write a custom file
>> copier,
>
> man cp on a System that has a recent cp. What System and Qt are you
> using? What version of cp?
>
> Andreas
--
[ signature omitted ]
Message 8 in thread
On 30.06.07 12:35:17, Keith Esau wrote:
> That is an option I've never seen. Here is the man page from Mac OS 10.4.10
> (about as recent as you can get, updated last week):
>
> CP(1) BSD General Commands Manual
> CP(1)
>
> NAME
> cp -- copy files
Well, thats obviously a differnce between MacOS and Linux:
CP(1) User Commands CP(1)
NAME
cp - copy files and directories
SYNOPSIS
cp [OPTION]... [-T] SOURCE DEST
[....]
--parents
use full source file name under DIRECTORY
Anyway, qmake only uses this option when generating unix makefile's, so
this shouldn't happen on MacOSX when using the proper mkspecs.
Andeas
--
[ signature omitted ]
