.o files not being generated on Linux

[PLL3]

Hi everyone,

I'm trying to fix an issue I have.

To fix it on Windows I needed to link not only the .lib files I produced but also some .obj file, for example

QtInstallFolder\lib\objects-Release\Widgets_resources_1\.rcc\qrc_qstyle.cpp.obj

However when trying to apply this on Linux, the folder at "QtInstallFolder/lib/objects-Release/Widgets_resources_1" is empty.

My question is the following: Why are my .o file not being generated ? How can generate or access them ?

Here's my configure script:

configure -prefix QtInstallFolder -release -static -feature-relocatable -submodules qtbase,qtsvg -no-opengl -cmake-generator Ninja -accessibility

followed by

cmake --build . --parallel
cmake --install .

Thanks in advance for the help :)

[SGaist]

Hi,

There's no reason to have any .o files in your installation folder. Static libraries end with .a on Linux.

[PLL3]

@SGaist Hi, thanks for the reply !

Is there no way for me to get those .o, like i get some .obj on Windows ? Because I really need to fix this issue.

[JonB]

@PLL3 said in .o files not being generated on Linux:

QtInstallFolder\lib\objects-Release\Widgets_resources_1\.rcc\qrc_qstyle.cpp.obj

the folder at "QtInstallFolder/lib/objects-Release/Widgets_resources_1" is empty.

Is it? If .o files are supposed to be in Widgets_resources_1\.rcc don't forget that under Linux directories beginning with . are "hidden", how did you check Widgets_resources_1 is empty?

Use find if you can't spot where .o files might be? Look at the compilation action lines to see what it is doing if you cannot find .o files you expect to be left around.

[PLL3]

@JonB said in .o files not being generated on Linux:

don't forget that under Linux directories beginning with . are "hidden"

Today I learned I guess. Evidently I'm not very familiar with Linux, I feel dumb now.

Second time you point me right to the solution thanks. I'd buy you a drink if I could :)

[JonB]

@PLL3
While PC/Windows/DOS has a "hidden" attribute on files/directories, to stop them being listed by default, Linux has no such file attribute. The convention is that programs like ls do not list files/directories staring with ., to allow user/programs to sort of hide files by default. Some desktop file explorers have an option to hide these (default is on), you can change that; ls accepts a -a option to list "all" files. find prints all filenames.

The choice here of .rcc may have only been with Windows, not Linux, in mind, I don't know.

You don't have to feel dumb about this one :)