Hi
We develop a Visual C++ project that, in one project configuration, uses a
small vendor library that is subject to export control. This means that we
can't let all developers on the project see that library. Everyone can build
with some build configurations but only some developers can bui
Hi, David,
Von: David Aldrich [mailto:david.aldr...@emea.nec.com]
> We develop a Visual C++ project that, in one project configuration, uses a
> small vendor library that is subject to export control. This means that we
> can't let all developers on the project see that library. Everyone can
On 24 March 2014 01:21, Daniel Shahaf wrote:
> Daniel Shahaf wrote on Sun, Mar 23, 2014 at 02:34:35 +:
>> sebb wrote on Sat, Mar 22, 2014 at 01:28:33 +:
>> > To reproduce the problem, start as follows:
>> >
>> > svn co http://dist.apache.org/repos/dist/release/commons/dbcp/@4582
>> >
>> >
On 23 March 2014 11:18, Philip Martin wrote:
> Daniel Shahaf writes:
>
>> sebb wrote on Sat, Mar 22, 2014 at 01:28:33 +:
>>> To reproduce the problem, start as follows:
>>>
>>> svn co http://dist.apache.org/repos/dist/release/commons/dbcp/@4582
>>>
>>> Then apply the following revisions in or
sebb writes:
> So what is the next stage in getting this inconsistency fixed ?
> Do I have to create a Bugzilla entry or will someone else take care of that?
I've done it: http://subversion.tigris.org/issues/show_bug.cgi?id=4482
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Dat
Another approach is to import the libraries into a vendor branch in your
project including the header files and everything else required for build.
Every time this protected library is rebuild you import the bins again into the
vendor branch. It is a good advice to always create a new folder in
