blocks|key|715992|text|您是否考虑过使用Qt+Creator作为构建环境和IDE？我个人从来没有在Ubuntu上使用过它，但我在Windows和g%2B%2B上使用过它，它在那里工作得很好。而且它似乎已经可以作为package+in+the+repository使用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|715993|您通过使用它获得的一些优势包括：|715994|715995|Qt创建器将(通常)为您管理.pro文件。(如果你像我一样，你仍然可以在这里添加很多额外的东西，但是当它们被添加到项目中时，它会自动添加.cpp、.h和.ui文件。)|unordered-list-item|715996|你可以设置项目间的依赖关系，这些依赖关系将以它们需要链接的任何顺序构建项目。|715997|你可以使用它与gdb的集成来单步执行和调试代码，以及跳转到代码。|715998|你可以在Qt信号和插槽上自动完成，以及内联语法突出显示和一些错误检查。|715999|如果你正在做.ui，您可以使用集成设计器对窗体进行可视化布局和设计。|716000|716001|回到你的实际问题，我认为当链接失败时，标志不可能告诉gcc不要出错，因为链接器没有办法懒惰地链接库。如果它链接到静态库(.a)，那么它需要能够将该代码的实现实际复制到可执行文件/库中。如果它是动态链接(.so)，它仍然需要验证所需的函数是否确实存在于库中。如果在链接步骤中不能链接，什么时候可以链接？|716002|事后想一想，如果你的编译过程中有循环依赖(A依赖于B，B依赖于C，C依赖于A)，那么你可能需要首先构建一个伪版本的库，它只有每个函数的实现的空存根，以及每个类或对象的完整定义。然后，在链接到该库的同时构建其他所有内容，最后，构建伪库的真实版本，并将其链接到已链接的所有其他版本。不过，我认为这只适用于动态链接。|716003|entityMap|0|LINK|mutability|MUTABLE|url|http://packages.ubuntu.com/search?keywords=qtcreator^0|2I|P|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|19|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|1A|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|1B|8|@]|9|@]|C|$]]|$1|L|3|M|5|I|7|1C|8|@]|9|@]|C|$]]|$1|N|3|O|5|I|7|1D|8|@]|9|@]|C|$]]|$1|P|3|Q|5|I|7|1E|8|@]|9|@]|C|$]]|$1|R|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|1G|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|1H|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

Have you looked into using Qt Creator as a build environment and IDE? I've personally never used it for development on Ubuntu, but I have used it on Windows with g++, and it works great there. And it appears its already available as a <a href="http://packages.ubuntu.com/search?keywords=qtcreator" rel="nofollow">package in the repository</a>.

Some of the advantages you get by using it are:

<ul>
<li>Qt Creator will (generally) manage the .pro files for you. (If you're like me, you can still add lots of extra stuff here, but it will automatically add .cpp, .h, and .ui files as they are added to the project.)</li>
<li>You can set up inter-project dependencies that will build projects in whatever order they need to link.</li>
<li>You can use its integration with gdb to step through and debug code, as well as jump to the code.</li>
<li>You get autocomplete on Qt signals and slots, as well as inline syntax highlighting and some error checking.</li>
<li>If you're doing GUIs, you can use the integrated designer to visually layout and design your forms.</li>
</ul>

Referring back to your actual question, I don't think it's possible for a flag to tell gcc to not error when a link fails simply because there is no way for the linker to lazily link libraries. If its linking to static libraries (.a), then it needs to be able to actually copy the implementation of that code into the executable/library. If its dynamically linking (.so), it still needs to verify that the required functions actually exist in the library. If it can't link it during the linkage step, when can it link?

As a bit of an afterthought, if there are cyclic dependencies in your compile process (A depends on B, B on C, and C on A), then you might need to have a fake version of a library get built first, which only has empty stubs for the implementation of each function, and the full definition for each class or object. Then, build everything else while linking to that, and at the end, build the real version of the fake library, and link it to all the other versions that were already linked. I think this would only work on dynamic linking, though.

blocks|key|4316548|text|您可以使用子目录项目来控制构建顺序(无论其他开发人员是否需要它:)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4316549|例如。|4316550|build_all.pro|4316551|TEMPLATE=subdirs
CONFIG%2B=ordered
SUBDIRS=lib2/lib2.pro+lib1/lib1.pro+app/app.pro|code-block|syntax|javascript|4316552|lib1.pro，lib2.pro，...是你生成的pro文件。然后对build_all.pro运行一次qmake，并在该目录中运行make。这将在lib1之前构建lib2，然后构建app。|4316553|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You could use a subdirs project to have control over the build order (no matter whether the other dev wants it or not :) ).

E.g.

build_all.pro

<pre><code>TEMPLATE=subdirs
CONFIG+=ordered
SUBDIRS=lib2/lib2.pro lib1/lib1.pro app/app.pro
</code></pre>

The lib1.pro, lib2.pro, ... are your generated pro files.
Then run qmake once for the build_all.pro and also run make in that directory. This will build lib2 before lib1 and then app.

Im helping on a c++ application. The application is very large and is spread out between different sub directories. It uses a script to auto generate qt .pro files for each project directory and uses qmake to then generate make files. Currently the libraries are being compiled in alphabetical order.. which is obviously causing linking errors when a library its trying to link isn't built yet.. Is there some kind of g++ flag i can set so it wont error out if a library its trying to link hasn't been built yet? or a way to make it build dependencies first through the qt .pro file?

NOTE:
This script works fine on ubuntu 10.10 because the statements to build the shared libraries didnt require that i use -l(libraryname) to link to my other libraries but ubuntu 11.10 does so it was giving me undefined reference errors when compiling on 11.10.

g++ linking .so libraries that may not be compiled yet

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在帮助开发一个c++应用程序。应用程序非常大，并且分布在不同的子目录中。它使用脚本为每个项目目录自动生成qt .pro文件，然后使用qmake生成make文件。目前，这些库正在按字母顺序进行编译。当它试图链接的库尚未构建时，这显然会导致链接错误。是否有某种类型的g++标志我可以设置，这样它就不会在试图链接的库还没有...

问链接可能尚未编译的.so库的g++
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问链接可能尚未编译的.so库的g++EN