If you'd read on, you would see that I first CREATE a tar file, then
EXTRACT it and then show that the contents have been restored.
Michael
On 25. Nov, 2009, at 14:56 , Brian J. Davis wrote:
In your example you use "cvf". This creates a tar file which is not
what I want to do. I want t
Works fine for me on my Mac. Can't help with Windows 7 (or rather,
6.1, but then the marketing guys at MS probably figured to round that
up to 7... ;-)) as I don't have access to it.
$ mkdir test
$ echo "Hello World" > test/hello.txt
$ cmake -E tar cvf test.tar test
drwxr-xr-x mwildstaff
"cmake -E tar xvf" is implemented...
Does this happen with other tar files, or just that one?
On Tue, Nov 24, 2009 at 11:07 PM, Brian Davis wrote:
> So I found this thread below and tried the command at the promp (Win7):
>
> cmake -E tar xvf
>
> CMake Error: Problem with tar_open(): No such fi
So I found this thread below and tried the command at the promp (Win7):
cmake -E tar xvf
CMake Error: Problem with tar_open(): No such file or directory
CMake Error: Problem extracting tar: ${TARDIR}/mytar.tar
cmake -E tar xvf openssl-0.9.8a.tar
CMake Error: Problem with tar_open(): No such fil
On 25. Mar, 2009, at 10:28, ankit jain wrote:
2009/3/25 Michael Wild
On 25. Mar, 2009, at 9:33, ankit jain wrote:
2009/3/25 Michael Wild
[...]
What I usually do is this:
add_custom_command( OUTPUT ${TARDIR}/t1
COMMAND ${CMAKE_COMMAND} -E tar xvf ${TARDIR}/mytar.tar
WORKING_DIRECTO
2009/3/25 Michael Wild
>
> On 25. Mar, 2009, at 9:33, ankit jain wrote:
>
> 2009/3/25 Michael Wild
>>
>
> [...]
>
>
>>> What I usually do is this:
>>>
>>> add_custom_command( OUTPUT ${TARDIR}/t1
>>> COMMAND ${CMAKE_COMMAND} -E tar xvf ${TARDIR}/mytar.tar
>>> WORKING_DIRECTORY ${TARDIR}
>>> COMME
On 25. Mar, 2009, at 9:33, ankit jain wrote:
2009/3/25 Michael Wild
[...]
What I usually do is this:
add_custom_command( OUTPUT ${TARDIR}/t1
COMMAND ${CMAKE_COMMAND} -E tar xvf ${TARDIR}/mytar.tar
WORKING_DIRECTORY ${TARDIR}
COMMENT "Extracting ${TARDIR}/mytar.tar"
VERBATIM
)
add_custom
2009/3/25 Michael Wild
>
> On 25. Mar, 2009, at 7:51, ankit jain wrote:
>
> 2009/3/25 Alexander Neundorf
>>
>> On Tuesday 24 March 2009, ankit jain wrote:
>>>
hi all,
Iam doing the following through my cmakelist.txt
add_custom_target(mytarget)
add_custom_command(TAR
On 25. Mar, 2009, at 7:51, ankit jain wrote:
2009/3/25 Alexander Neundorf
On Tuesday 24 March 2009, ankit jain wrote:
hi all,
Iam doing the following through my cmakelist.txt
add_custom_target(mytarget)
add_custom_command(TARGET mytarget POST_BUILD
COMMAND ${CMAKE_COMMAND} -E tar xvf ${CM
2009/3/25 Alexander Neundorf
> On Tuesday 24 March 2009, ankit jain wrote:
> > hi all,
> >
> > Iam doing the following through my cmakelist.txt
> >
> > add_custom_target(mytarget)
> > add_custom_command(TARGET mytarget POST_BUILD
> > COMMAND ${CMAKE_COMMAND} -E tar xvf ${CMAKE_CURRENT_SOURCE_DIR}
On Tuesday 24 March 2009, ankit jain wrote:
> hi all,
>
> Iam doing the following through my cmakelist.txt
>
> add_custom_target(mytarget)
> add_custom_command(TARGET mytarget POST_BUILD
> COMMAND ${CMAKE_COMMAND} -E tar xvf ${CMAKE_CURRENT_SOURCE_DIR}/t1.tar)
> this cmakelist is written in subfold
hi all,
Iam doing the following through my cmakelist.txt
add_custom_target(mytarget)
add_custom_command(TARGET mytarget POST_BUILD
COMMAND ${CMAKE_COMMAND} -E tar xvf ${CMAKE_CURRENT_SOURCE_DIR}/t1.tar)
this cmakelist is written in subfolder of a mainfolder..
But the problem is that files are no
12 matches
Mail list logo