1. Are the (T)Qt3 bin files used only during compiling or are they used during run-time as well?
2. Is there a configuration option to not build the html files? I do not notice anything obvious. I have been deleting the files in my build script after completing make because they add 5MB+ to the package size. (I don't want to strip the files into a separate package.)
3. Have the html files been updated to include changes/additions made in the Trinity versions?
Thanks!
Darrell
- Are the (T)Qt3 bin files used only
during compiling or are they used during run-time as well?
- Is there a configuration option to not build the html
files? I do not notice anything obvious. I have been deleting the files in my build script after completing make because they add 5MB+ to the package size. (I don't want to strip the files into a separate package.)
- Have the html files been updated to include
changes/additions made in the Trinity versions?
Anybody?
Darrell
- Are the (T)Qt3 bin files used only
during compiling or are they used during run-time as well?
- Is there a configuration option to not build the html
files? I do not notice anything obvious. I have been deleting the files in my build script after completing make because they add 5MB+ to the package size. (I don't want to strip the files into a separate package.)
- Have the html files been updated to include
changes/additions made in the Trinity versions?
Anybody?
Darrell
- Are the (T)Qt3 bin files used only
during compiling or are they used during run-time as well?
- Is there a configuration option to not build the html
files? I do not notice anything obvious. I have been deleting the files in my build script after completing make because they add 5MB+ to the package size. (I don't want to strip the files into a separate package.)
- Have the html files been updated to include
changes/additions made in the Trinity versions?
Anybody?
Darrell
1.) bin files? Can you be more specific? :-)
2.) Not that I am aware of; most packaging scripts split them off or delete them entirely.
3.) Probably not (i.e. I have not touched them, but I don't know if Qt regenerates them during the build process via doxygen).
Tim
1.) bin files? Can you be more specific? :-)
assistant, createcw, designer ... moc, qembed, qmake ... uic
Darrell
Many of those files are used during the build process of any Qt3-dependent applications, including ALL TDE libraries and applications.
Tim
1.) bin files? Can you be more specific? :-)
assistant, createcw, designer ... moc, qembed, qmake ... uic
Many of those files are used during the build process of any Qt3-dependent applications, including ALL TDE libraries and applications.
Yes, that I knew, but are any of those files used during run-time by apps? Or are they used only when compiling TQt3 dependent apps?
I ask because I am contemplating the idea of renaming those 16 files. Perhaps prefix them all with a "t" like your script wrapper tmoc (which, with renaming moc would no longer be necessary).
Darrell
1.) bin files? Can you be more specific? :-)
assistant, createcw, designer ... moc, qembed, qmake ... uic
Many of those files are used during the build process of any Qt3-dependent applications, including ALL TDE libraries and applications.
Yes, that I knew, but are any of those files used during run-time by apps? Or are they used only when compiling TQt3 dependent apps?
I ask because I am contemplating the idea of renaming those 16 files. Perhaps prefix them all with a "t" like your script wrapper tmoc (which, with renaming moc would no longer be necessary).
Darrell
I don't believe any are used at runtime, and therefore they all could safely be renamed.
Tim
assistant, createcw, designer ... moc, qembed, qmake ... uic
Many of those files are used during the build process of any Qt3-dependent applications, including ALL TDE libraries and applications.
Yes, that I knew, but are any of those files used during run-time by apps? Or are they used only when compiling TQt3 dependent apps?
I ask because I am contemplating the idea of renaming those 16 files. Perhaps prefix them all with a "t" like your script wrapper tmoc (which, with renaming moc would no longer be necessary).
I don't believe any are used at runtime, and therefore they all could safely be renamed.
Should we do that? Could we do that?
I asked the question because of bug report 843. I'm always looking for potential conflicts with KDE4 and renaming those bin files would remove one more layer. Just one layer, but removed nonetheless.
Rename all 16 files with a "t" or "tde" or "tq" prefix. Nothing fancy. Maybe that means bumping (T)Qt3 to version 3.4.1....
What is needed to test this idea?
Darrell
-
Darrell Anderson -
Timothy Pearson