From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id B3CC8E0076B; Tue, 14 Apr 2015 08:33:52 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (nickaein.i[at]gmail.com) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.214.181 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3F83CE003A8 for ; Tue, 14 Apr 2015 08:33:50 -0700 (PDT) Received: by obbeb7 with SMTP id eb7so4458759obb.3 for ; Tue, 14 Apr 2015 08:33:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=hGLIJI1r7Q+/bkev/W6Yq2jbcRyGfx1XiExGG3yC7zE=; b=PXvUAFmG0dG5EOBaOIjqn4SkUljxCEJsXhYiIrz4wNPsu4aXfSgETn12nQWy9liXTN VciZ1hJPGP2hsL5DY6GKJrpFor0F2RHqT/HEJ6i75eGrrSNEryo1YZygyU2piNvqK2YZ 7ekoBHMW9eXQtsYzIpkbLEyVcbRNiu5QzcfS8hPdyMPUwQdR9uLirlvHh0UCdliBXXIT 2M9UmmALMwi6AZubp91cjrFdllMhUsenq+5yjP3O0bDcoxBue/Dn01rtI1DpcYC1y5jR +RYcPC1wWuYN2W3Xpg87wWL+OIMjBcz9ftSidIy7fpF/8159KaEWfzIMd9+Z05ogvHhJ VcNQ== X-Received: by 10.60.145.137 with SMTP id su9mr16729279oeb.40.1429025630035; Tue, 14 Apr 2015 08:33:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.104.37 with HTTP; Tue, 14 Apr 2015 08:33:29 -0700 (PDT) In-Reply-To: References: From: Isaac Nickaein Date: Tue, 14 Apr 2015 20:03:29 +0430 Message-ID: To: Otavio Salvador Cc: "meta-freescale@yoctoproject.org" Subject: Re: Recipe for a toolchain with static qt build X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2015 15:33:52 -0000 Content-Type: text/plain; charset=UTF-8 I am looking for a way to reduce size of my Qt application binary. Statically compiling the program will result an overall smaller output. For instance, I have to copy the whole QtGui.so, QtNetwork.so, etc, even when I am using very small part of them. However, in static compilation the linker can eliminate unnecessary codes from the output. I am also curios that how it can/should be done to best honest, On Tue, Apr 14, 2015 at 4:13 PM, Otavio Salvador wrote: > On Tue, Apr 14, 2015 at 7:40 AM, Isaac Nickaein wrote: >> Hi, >> >> I've successfully built a toolchain with Qt support using: >> >> bitbake meta-toolchain-qte >> >> And cross-compiled a Qt program. Thanks Yocto for that! >> >> >> As the built Qt is static, I currently have to copy Qt library >> dependencies (e.g. libQtGuiE.so) to the rootfs by hand (is there a >> better way?) >> >> Is there any meta-toolchain recipe for Qt static build? I hope that >> help me to save a little more space, since the linker will remove >> unnecessary codes from each library. > > I am not following your view here. What are you intending to accomplish? > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.br http://code.ossystems.com.br > Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750