| 3 | | Regarding Perl. Yes, I noticed that too. The reason is that the original qconfig.h file the forwarders refer to, does not yet exist (the syncqt script even emits a warning in such a case) as according to configure logic it is created at a later stage. So, as a solution, in r995 I now create an empty dummy qconfig.h before executing syncqt. Its date will be a few minutes earlier than the real config.h but for the make sake it's OK -- the problem only takes place where you initiate the build directory for the first time (nothing is built anyway), subsequent runs of syncqt will take the actual date of qconfig.h if it gets changed (or leave the forwarder untouched). This also fixes the Perl warning about an uninitialized variable at line 337 (a cross-platform bug |
| | 3 | Regarding Perl. Yes, I noticed that too. The reason is that the original qconfig.h file the forwarders refer to, does not yet exist (the syncqt script even emits a warning in such a case) as according to configure logic it is created at a later stage. So, as a solution, in r995 I now create an empty dummy qconfig.h before executing syncqt. Its date will be a few minutes earlier than the real config.h but for the make sake it's OK -- the problem only takes place where you initiate the build directory for the first time (nothing is built anyway), subsequent runs of syncqt will take the actual date of qconfig.h if it gets changed (or leave the forwarder untouched). This also fixes the Perl warning about an uninitialized variable at line 337 (a cross-platform bug in syncqt). |
