Menu
▾
▴
Re: [proteowizard-support] Cannot compile
|
From: Alexandre B. <a....@un...> - 2019-03-25 07:20:25
|
Not every time. Ive just checked with other log files I still have from
last week and I could only find one similar failure:
common.hard-link
D:\workspace\pwiz.git\trunk\build-nt-x86\pwiz\data\vendor_readers\UIMF\Reade
r_UIMF_Test.test\msvc-14.1\release\address-model-64\asynch-exceptions-on\lin
k-static\threading-multi\SQLite_v1.0.98\System.Data.SQLite.DLL
if not exist
"D:\workspace\pwiz.git\trunk\build-nt-x86\pwiz\data\vendor_readers\Waters\Re
ader_Waters_Test.test\msvc-14.1\release\address-model-64\asynch-exceptions-o
n\\" mkdir
"D:\workspace\pwiz.git\trunk\build-nt-x86\pwiz\data\vendor_readers\Waters\Re
ader_Waters_Test.test\msvc-14.1\release\address-model-64\asynch-exceptions-o
n"
...failed common.mkdir
D:\workspace\pwiz.git\trunk\build-nt-x86\pwiz\data\vendor_readers\Waters\Rea
der_Waters_Test.test\msvc-14.1\release\address-model-64\asynch-exceptions-on
...
The strange thing is that the directory actually exists and it only contains
".\Reader_Waters_Test.test\msvc-14.1\release\address-model-64\asynch-excepti
ons-on\link-static\threading-multi\SQLite_v1.0.98\System.Data.SQLite.DLL".
The creation date from Windows properties says that it was created just
seconds after the Thermo and UIMF asynch-exceptions-on directories (in the
log file, they are created just before the failure appears).
It makes no sense to me !
Hopefully, building msconvert only seems to work so Im not stuck here. But
its hard to be satisfied when something is not working as it should J
De : Chambers, Matthew [mailto:mat...@gm...]
Envoyé : vendredi 22 mars 2019 17:06
À : Alexandre Burel <a....@un...>; su...@pr...
Objet : Re: [proteowizard-support] Cannot compile
common.hard-link
D:\workspace\pwiz.git\trunk\build-nt-x86\pwiz\utility\bindings\CLI\analysis\
msvc-14.1\release\address-model-64\link-static\threading-multi\using-clr-tru
e\SQLite_v1.0.98\System.Data.SQLite.DLL
...on 5100th target...
if not exist
"D:\workspace\pwiz.git\trunk\build-nt-x86\pwiz\utility\bindings\CLI\analysis
\SpectrumList_IonMobility_Test.test\msvc-14.1\\" mkdir
"D:\workspace\pwiz.git\trunk\build-nt-x86\pwiz\utility\bindings\CLI\analysis
\SpectrumList_IonMobility_Test.test\msvc-14.1"
...failed common.mkdir
D:\workspace\pwiz.git\trunk\build-nt-x86\pwiz\utility\bindings\CLI\analysis\
SpectrumList_IonMobility_Test.test\msvc-14.1...
You're saying this error happens every time you run?
On 3/22/2019 11:23 AM, Alexandre Burel wrote:
Hi Matt,
Thank you for your fast answer !
Here are some comments on your suggestions:
It works well when I only try to compile msconvert, which should fit my
needs so I may focus on this solution J
I was convinced that I had already install the .NET framework 4.7.2 but I
could not see it in the application list so I installed the developer pack
But I did it after building successfully msconvert so maybe it was not
necessary.
I did not see the mkdir issue but I can tell you that it did not disappear
after rebuild as Ive been trying to build all this week :p So maybe a
configuration problem on my side ?
I keep on building, it helps a lot to have a fresh look, thank you again !
Alex
De : Chambers, Matthew [mailto:mat...@gm...]
Envoyé : vendredi 22 mars 2019 15:19
À : Alexandre Burel <mailto:a....@un...> <a....@un...>;
su...@pr... <mailto:su...@pr...>
Objet : Re: [proteowizard-support] Cannot compile
Hi Alexandre,
A couple issues here:
1. When you run quickbuild with no specific targets, it builds everything:
all tests, all command-line executables, all .NET applications. If you're
interested in a particular target, specify it like
path/to/target//target_name (e.g. pwiz/data/msdata//MSDataTest; there are
some convenience aliases like 'msconvert' and 'executables' too).
2. I read your log file and it looks like there's some errors building the
.NET applications (search for "...failed" in the log). Do you have the 4.7.2
targeting pack installed? There's a few other errors, one of which is an
elusive mkdir failure which I've only ever seen on our TeamCity builds,
which will go away if you run the build again. The others look like they may
be consequential from the .NET failures. Fix the .NET failures and see what
other errors you get. Or, if you narrow down your target build list, you
probably already have built what you want.
Hope this helps,
-Matt
On 3/22/2019 10:11 AM, Alexandre Burel wrote:
Hi,
I have been trying to compile Proteowizard and I just cant manage to do it.
I updated from the trunk the other day, I have Visual Studio 2017, and I
run the following command:
quickbuild -j5 toolset=msvc-14.1 address-model=64
--i-agree-to-the-vendor-licenses > quickbuild.log 2>&1
It takes about an hour and at the end I get a huge log file, which ends with
this: ...failed updating 17 targets...
The complete log file can be downloaded here:
https://filesender.renater.fr/?s=download
<https://filesender.renater.fr/?s=download&token=aaed662b-110d-395d-70ae-e89
7ce9f3916> &token=aaed662b-110d-395d-70ae-e897ce9f3916
Im sure you dont want to read the 13k lines of the log file, so Im only
asking if you can tell me more about the environment you use to compile
Proteowizard ? Or maybe share with me the command lines you use, or the log
file you get so I can compare and try to see where it starts to differ ?
Any new ideas would be highly appreciated J
Thank you !
_______________________________________________
proteowizard-support mailing list
pro...@li...
<mailto:pro...@li...>
https://lists.sourceforge.net/lists/listinfo/proteowizard-support
|
