Adding lib files and their paths in .pro file [Closed]
-
There are several ways to do this. Do you want a full-fledged library, or just use different .pro files for your components? I use the second way frequently.
Instead of using a .pro file, I use a .pri file. They are the same format, but a .pri file is semantically different. It does not describe a complete project, it only describes what is needed for a single component that I may use in several projects. A typical .pri file might look like this for me:
@
SOURCES *= src/fileselector.cpp
HEADERS *= src/fileselector.h
FORMS *= ui/fileSelectorUI.ui
@Then, in the project where I want to use this component, I have this in the .pro file (along with everything else that needs to be in the .pro file to make it a complete project, of course):
@
VPATH = ../common/
INCLUDEPATH += ../common/src/include(../common/fileselector.pri)
@In my source, where I use this component, I then only need to do this:
@
#include "fileselector.h"
@and I can access everything I need from the FileSelector component. I am currently using this pattern for about 30 components that I use across 10 or so applications, so I can vouch for this method working.
A downside to this method is that if you change something in a component, you need to re-compile all the applications that use that component. Also, each component is re-compiled for every application. If you put the component in a real library, you only need to compile it once when it changes. Also, if you have several of these different applications sharing the same components open at the same time, you can share the memory needed for them.
-
hey gerolf,I am sorry but if you r with me,we will go from first,
now I have created freshly two projects and named as test1 and test2.which contains nothing.now tell me what is my first step and whether i have to create lib file?I will go as per your instructions,
regards
imrrk -
-
hey andre i have created a .pri file as per your instructions,my test11.pri looks like below
@SOURCES *= dialog.cpp
HEADERS *= dialog.h
FORMS *= dialog.ui@
now in your above post u said to add these in my main project ie. test2.pro file..so how shall i include it according to you -
- ../common/ is the directory where all my .pri files are. You need this to have qmake find your source files.
- ../common/src is the directory where all the source and header files for my components are. You need that to be able to #include them.
- the include statement actually pulls in the contents of the .pri file into the .pro file.
So, what you put where, depends on where your components are in your file structure. In my case, I have something like this as my root structure:
@
common
common/src
common/ui
common/resources
project1
project1/src
project2
project2/src
project2/ui
project2/resources
@
etc. The .pri files are in the directory common, while the .pro files are in the different project directories (project1 and project2). -
ok andre i got your point and i have included in my main project i.e test2.pro file the below lines
@INCLUDEPATH += ../test11
include(../test11.pri)@and in my main project ie test2,i have dialog1.cpp and i have include this code
@#include "dialog1.h"
#include "ui_dialog1.h"#include "dialog.h"//this is from my previous project test11
Dialog1::Dialog1(QWidget *parent) :
QDialog(parent),
ui(new Ui::Dialog1)
{
ui->setupUi(this);
}Dialog1::~Dialog1()
{
delete ui;
}void Dialog1::on_pushButton_clicked()
{
Dialog a(this);
a.show();
a.exec();
}@
now only one error i am getting
bq. :: error: collect2: ld returned 1 exit statuswhether i am on the right track?
regards
imrrk -
Do yourself and all contributors here a favor and start from scratch. Your baby project does not need to be split up into a myriad of single subprojects including DLLs (you will not bother us with DLL, library and plugin errors, won't you?).
Collect all the relevatn .cpp and .h files, put them into a single directory and make a single project out of it by writing a new .pro file from scratch.
Sorry if I sound a bit rude, but from your knowledge of Qt in particular and C++ and development skills in general you are far far away from being able to manage project with subprojects.
-
-
volker,i think many things will be new to everyone in this world,few things might be new to you also,and if i need to learn it i have to,i cant follow the alternate approach,if i will i can achieve it ,and i am not rude and angry on anyone,and and you masters can only help us beginners to become masters like you and I think by sharing knowledge only knowledge increase.`So I want to learn it and I will learn it
thanks
imrrk -
Did you find out what your linker error is about yet? What file or method is your linker complaining about?
imrrk, as you have been told before, you're not an easy one to provide help to. You respond badly to suggestions, and show very, very little understanding of programming in general, programing in C++ in particular and of Qt especially, nor an inclination to do some research of your own. That is tiresome for people trying to help you, and takes away from the attention more advanced people on this forum can give to other people asking questions. I'm sure you have been referred to "this FAQ":http://www.catb.org/~esr/faqs/smart-questions.html before, but I will again. Please read it carefully. It may help you understand why people here sometimes get frustrated with the stream of questions that you post here (and in other places, I understand).
-
hello andre,I solved the error,thanks a lot,actually andre I am still a learner,and I aplogize if I have gone wrong in communicating..Now I am able to open a dialog present in another project on a button click.
now similarly I tried to open a mainwindow.ui present in another project by the below code@void Dialog1::on_pushButton_2_clicked()
{
MainWindow *b=new MainWindow;
b->showMaximized();
}@
and i succeed in opening the mainwindow,but the issue is that the size shrinks when it gets open,may i know the reason for this.regards
imrrk