Changeset 89
- Timestamp:
- Apr 17, 2006, 8:41:04 PM (19 years ago)
- Location:
- trunk
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/os2-doc/doc.html
r66 r89 335 335 <code>$(RES_FILE)</code> to specify the <kbd>.res</kbd> file to bind and 336 336 <code>$(TARGET)</code> to specify the executable file name.</p> 337 338 <p>20. Added the internal qmake variable 339 <code>QMAKE_LIBDIR_QT_DEBUG</code>. It defines where to place the Qt 340 library when the debug version is being built, and also where to search 341 for it when the project file of an application contains <kbd>qt</kbd> and 342 <kbd>debug</kbd> keywords in the <code>CONFIG</code> statement.</p> 343 344 <p>21. The <code>VERSION</code> project variable is copied by qmake (as 345 is) to the generated makefile. Note that its value does not affect the 346 name of the generated DLL target anymore (for projects with the 347 <kbd>lib</kbd> template and with the <kbd>dll</kbd> keyword in 348 <code>CONFIG</code>), as opposed to other qmake backends. Appending a 349 version number to the DLL name could implicitly lead to running out of the 350 8x3 naming limit that is still present in OS/2 for DLLs loaded by module 351 name (the most common case). Instead, the <code>VERSION</code> macro can 352 be used by qmake compiler specifications to embed the version to the 353 generated DLL file itself (as the GCC specification does).</p> 337 354 </body> 338 355 </html> -
trunk/qmake/generators/os2/gnumake.cpp
r85 r89 229 229 t << project->variables()[ "TARGET" ].first() << project->variables()[ "TARGET_EXT" ].first(); 230 230 t << endl; 231 232 if ( !project->isEmpty( "VERSION" ) ) { 233 t << "VERSION = " << var("VERSION") << endl; 234 } 231 235 t << endl; 232 236
Note:
See TracChangeset
for help on using the changeset viewer.