Cannot disable preview

[MattHawkinsUK]

Thanks everyone for the tips. I've managed to edit and recompile my RaspiStill utility following m1m1's instructions although I had to sudo the apt-get and make commands plus install cmake. I skipped the git clone because I already had the userland zip file which I copied across using WinSCP.

Being able to do this myself is great because now I can tinker with the apps and make some customisations!

A few things that spring to mind are changing the default command line option values and padding the number inserted into the filename during time lapse still capture.

[jamesh]

The filename during timelapse it pretty versatile. It uses the same formatting as printf, so...

-o filename%d.jpg == filename1.jpg, filename2.jpg etc

-o filename%04d.jpg == filename0001.jpg, filename0002.jpg etc

-o filename%dplus.jpg == filename1plus.jpg, filename2plus.jpg etc

Look up printf formatting for more exciting options!

[Chris_Reynolds]

Re-read m1m1's instructions and it is building fine now - thanks again.

Now to look at the EXIF data.

[AMazinG]

Thanks all for your valious posts. m1m1 guide worked perfectly fine!!

[eckythump]

I also had success with m1m1's instructions, thanks indeed.

a bit off topic, but related:

it seems like the raspberry pi is going through quite a long-winded procedure (took about 30 minutes in total) just to make one change in a single .c file. Could anybody point me in the direction of a guide/tutorial that explains what is happening here and why these steps are necessary? Is there a faster way of testing the result of changing a line or two of code?

[Nu7s]

The filename during timelapse it pretty versatile. It uses the same formatting as printf, so...

-o filename%d.jpg == filename1.jpg, filename2.jpg etc

-o filename%04d.jpg == filename0001.jpg, filename0002.jpg etc

-o filename%dplus.jpg == filename1plus.jpg, filename2plus.jpg etc

Look up printf formatting for more exciting options!

Thanks, I was wondering about this.

[Chris_Reynolds]

I also had success with m1m1's instructions, thanks indeed.

a bit off topic, but related:

it seems like the raspberry pi is going through quite a long-winded procedure (took about 30 minutes in total) just to make one change in a single .c file. Could anybody point me in the direction of a guide/tutorial that explains what is happening here and why these steps are necessary? Is there a faster way of testing the result of changing a line or two of code?

I had a long compile the first time as none of the binaries for any of the userland code were there. After that the make file just whizzed through all the non-camera stuff and takes just a few seconds to build raspistill so my edit compile test cycle is fine now. Are you seeing it rebuild all of the code on each run of sudo make?

[eckythump]

I had a long compile the first time as none of the binaries for any of the userland code were there. After that the make file just whizzed through all the non-camera stuff and takes just a few seconds to build raspistill so my edit compile test cycle is fine now. Are you seeing it rebuild all of the code on each run of sudo make?

yes, when I make changes now it just takes about 20 seconds to do the whole thing, which is good to know,
thanks.

[giaoduong]

When I typed: sed -i ‘s/if (DEFINED CMAKE_TOOLCHAIN_FILE)/if (NOT DEFINED CMAKE_TOOLCHAIN_FILE)/g’ makefiles/cmake/arm-linux.cmake

It said: couldn’t open temporary file makefiles/cmake/seduMkbNy: Permission denied.

How could I solve it???
Thanks!

[DougieLawson]

It said: couldn’t open temporary file makefiles/cmake/seduMkbNy: Permission denied.

The ownership (or permission bits) for your makefiles/cmake directory is incorrect.

You can either
1. Use root (sudo sed ...) # this is badness.
2. Extract the tar.gz file using the user you're going to use to build the project
3. Use chown -R user.group * (to change the user and group in the whole build tree)