From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17458 invoked by alias); 20 Aug 2014 16:37:56 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 17437 invoked by uid 89); 20 Aug 2014 16:37:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: OARmail.OARCORP.com Received: from oarmail.oarcorp.com (HELO OARmail.OARCORP.com) (67.63.146.244) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 20 Aug 2014 16:37:54 +0000 Received: from [192.168.1.169] (192.168.1.169) by OARmail.OARCORP.com (192.168.2.2) with Microsoft SMTP Server (TLS) id 8.3.342.0; Wed, 20 Aug 2014 11:31:29 -0500 Message-ID: <53F4CEDE.3000208@oarcorp.com> Date: Wed, 20 Aug 2014 16:37:00 -0000 From: Joel Sherrill User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Joel Brobecker CC: Mike Frysinger , "gdb@sourceware.org" , Anthony Green Subject: Re: integrating dtc into the sim/ tree References: <53F27ADC.4070609@oarcorp.com> <1732783.0nBxt22mln@vapier> <20140820095347.GH4828@adacore.com> <1850909.FvmpfGFofc@vapier> <20140820160635.GK4828@adacore.com> <53F4C8A5.1070503@oarcorp.com> <20140820161921.GL4828@adacore.com> In-Reply-To: <20140820161921.GL4828@adacore.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-08/txt/msg00102.txt.bz2 On 8/20/2014 11:19 AM, Joel Brobecker wrote: >> I would have been happy if the generated files were in the tree and >> only maintainer mode would result in the dependencies being checked. >> >> This has precedence for other tools. > Is it just generated files? I was under the impression that you had > to link against a library as well. If that wasn't the case, then it > would certainly mitigate most of my concerns! > Inspecting the Makefile.in, I believe that is the case. This is all there is: moxie-gdb.dtb: moxie-gdb.dts dtc -O dtb -o moxie-gdb.dtb ${srcdir}/moxie-gdb.dts install-dtb: moxie-gdb.dtb $(SHELL) $(srcdir)/../../mkinstalldirs $(DESTDIR)$(dtbdir) $(INSTALL_DATA) moxie-gdb.dtb $(DESTDIR)$(dtbdir)/moxie-gdb.dtb No reference to libraries. I checked the generated moxie-gdb.dtb and it shows this: $ file moxie-gdb.dtb moxie-gdb.dtb: Device Tree Blob version 17, size=519, boot CPU=0, string block size=75, DT structure block size=388 I am nearly 100% sure this could be a maintainer only option. FWIW we have been looking into using dtc with RTEMS. It is a nice way to abstract away the particulars of a SoC and let the BSP/drivers find their properties from a configuration file/blob during initialization. But I don't know how this package is distributed. -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherrill@OARcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985