Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Their build is based on Visual Studio solution/project files (which I am not fond of to begin with) and these solution files to have the dependencies set. The problem is that some of these solutions weren't even built even though underlying static libraries they depended on had changed. The reason is because they don't build all applications, only the ones they think have changed and that they plan on releasing. There are a lot of things I'm working on fixing, source code control and the build are two of the first. Nick "Gerhard Fiedler" <lists at connectionbrazil.com> wrote in message news:9r6jzdtjanhf.dlg at connectionbrazil.com... > Nick Duane wrote: > >> Our project consists of several applications and several static libraries >> that most of these applications make use of. Currently when a release is >> done only the applications which have changes are built and released. >> I'm >> not sure if this is the best approach, as when I started working on >> cleaning >> up the build several applications no longer built because of changes that >> were made to the shared libraries. > > Don't you have the shared libs as dependencies in the build instructions > (make, ant, scons etc)? > > Gerhard