Implement something like tar archive in windows environment

[VRonin]

That error usually comes up when you mix 32 and 64 bits version of the libraries.

[Zgembo]

@VRonin Yes you are right. I have copied wrong dll to debug folder, so on runtime my app tried to open these 32-bit dlls.
Where is the best way to put these .dlls for production enviroment? Should I copy all these dlls to c:\windows\system32?

[jsulm]

@Zgembo said in Implement something like tar archive in windows environment:

Should I copy all these dlls to c:\windows\system32

Please not! :-)
Just put them in same directory where you have your executable.

[Zgembo]

@jsulm OK, thank you. What about my include files? Now I have my KArchive folder that have "include" and "libs" subfolders in my C:\Downloads folder. I have included this two folders with their absolute path into my project (visual studio project).
Is there a better way to do this, because this is a large project that have a lot of developers.

[VRonin]

@Zgembo said in Implement something like tar archive in windows environment:

because this is a large project that have a lot of developers.

Every project will have its own convention. just ask how you guys handle 3rd party libraries locations

[Zgembo]

OK, thank you. My test program now works in debug mode. I am having problems compiling program in RELEASE mode. For some reason it can not see qplatformdefs.h . I have double checked that path to that file is included as @VRonin stated in some of the previous posts.

[VRonin]

Visual studio uses different "Additional library directories" and "Additional include directories" for different platforms (x86 and x64) and configurations (Debug/Release) so every time you have to set the same thing multiple times for each of them using the comboboxes in the top part of the properties widow of the project

[Zgembo]

Figured it out. Everything works now. Thank you.

[SGaist]

IIRC, qmake can generate Visual Studio Solutions that should handle that for you. Worth a try at least.

[Zgembo]

I have moved everything to my main project and it works. Now I can tar and untar files form my main project.

Right now I am trying to figure out best way to indicate to a user that archiving or unarchiving process is in progress. I was thinking of using qprogressbar but I do not see a way to send any signal from KArchive function to qprogressbar.
Lets say that I have for example three large files to unarchive (few gigabytes). What would be the best way to somehow indicate to a user what is going on?

[mrjj]

@Zgembo
In cases where you cannot know the length of the process/get status,
you can use a QLabel with a animated gif.
like

[SGaist]

You can use a QProgressBar with both min and max set to 0. This will give you an "infinite" animated bar.

[Zgembo]

@SGaist I have tried your suggestion using "infinite" progress bar, but my tar and untar functions take a lot of processing power and animation is not working.

What would be the best way to move for example my two function to another thread? I have two function tarArchive(QString, QString) and unTarArchive(QString, QString).

[SGaist]

If you'd like to avoid your GUI freezing, then yes. However, you should take a look at QtConcurrent::run before diving into QThread.

[Zgembo]

I have tried QtConcurrent::run but I have to wait before the process (tar and untar) that I have moved to another thread finishes. So I have to use waitForFinished() and my GUI still freezes. Any suggestions?

[mrjj]

@Zgembo
Hi
Maybe you can use
http://doc.qt.io/qt-5/qfuturewatcher.html#details
to avoid the waitForFinished ?

[SGaist]

@Zgembo How did you implement that ?

[Zgembo]

@SGaist I figured out that first I have to change my program logic to implement QtConcurrent::run. Anyway thank you and @VRonin for all the help you provided in this thread. I will close it as solved.