In fact I think the issue is mainly with how ffmpeg compiles on older compilers and without c++11 explicitly requested, so I'm leaving it open. After updating and rebuilding all 3rd party packages (including ffmpeg), I now no longer have the issue I described, but that doesn't mean it's fixed in the sense that it can't occur again for someone else. I've since updated gcc to 8.3.0 (from 5.4), and I've given up on supporting older c++ compatibility below c++11 on linux. Update: The issue seems to be related to the version of C++ as was hinted at in the comments below. including time.h? Should I pin the time.h include for the system to the specific platform I'm compiling to? Should I go over all targets that possibly need time.h? Dancing elephants and confetti lie ahead. So, for a C++ setup linking with many 3rd party dependencies, what is the correct way to make sure everything keeps compiling w.r.t. I still get errors like:Įrror: field ‘st_atim’ has incomplete type ‘timespec’, struct timespec st_atim I've tried including all sorts of permutations of time.h/ctime and sys/time.h in a precompiled header that is referred to throughout the codebase. I've rewritten my CMake scripts, taking care to use dedicated include folder specs for most of the targets. Simply referring to usr/include/i386-linux-gnu as an include path thus becomes deadly, which is odd when referring to system includes. Also, Php-izing all sources does not sound like a solution at all.Īnother time.h exists in usr/include/i386-linux-gnu/bits on my system, so this isn't an ffmpeg-only phenomenon either. FFmpeg, the reasoning seems to be that an ugly hack is sufficient to fix the problem. If timep is NULL, the access and modification times are set to the current. cpp anywhere in your build stack ever includes a time.h, with the include path holding multiple valid entries ( including the one for ffmpeg), it may refer to the wrong one, and the declarations are simply replaced. The utime () function sets the access and modification times of the named file.
Ffmpeg (and some other libs) has it's own time.h, and even timeb.h. as part of ffmpeg-dev) it becomes clear that time.h was created to drive people nuts. if one installs and links with libavutil (e.g. This clock_gettime() is defined in time.h, see. Gettimeofday() has been discouraged, and is now currently enjoying deprecated status, so I should use clock_gettime() instead. I imagine the poster thinks that it allows you to link more 3rd party libaries that use particular functions like gettimeofday. This post says including sys/time.h improves portability. while this thread implies that sys/time.h must be included before sys/resources.h is included, in particular for BSD-based platforms. One SO post suggested that one should AVOID using the sys/* based includes alltogether. Time noun The property of a system which allows it to have more than one distinct configuration. ‘Time slows down when you approach the speed of light.’ Timing noun The time when something happens. The time.clock() time. Time noun Change associated with the second law of thermodynamics the physical and psychological result of increasing entropy.
So the time difference between the two calls is the complete time the system has elapsed. Technically you should be able to specify both. time.time() time.clock() The time.time() function is the wall clock time, which is the timestamp of the system clock. However, they both define the same function, albeit in a different namespace.
Some SO threads suggest that including ctime would be the right thing to do when writing C++ code, whereas you would still include time.h for C code. But in the first sentence, there is no 'the' before time: 'I don't have time to go on vacation. You do have time and money for other things, such as lunch.
UTIME VS TIME PORTABLE
I hope some Linux die-hard can answer me how I should write portable (POSIX) code when working with time functions. It's the time and the money because it's specifically the time and the money needed to go on vacation.
0 kommentar(er)
