Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add xerces-c #194

Closed
wants to merge 7 commits into from
Closed

Add xerces-c #194

wants to merge 7 commits into from

Conversation

groutr
Copy link
Contributor

@groutr groutr commented Mar 23, 2016

Split from #108

--disable-network \
--disable-static
make
make install
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make check?

@pelson
Copy link
Member

pelson commented Mar 25, 2016

Win failure:

msbuild projects\Win32\VC9\xerces-all\xerces-all.sln /t:all /p:Configuration=Release;Platform=Win32 
Microsoft (R) Build Engine Version 2.0.50727.8007
[Microsoft .NET Framework, Version 2.0.50727.8009]
Copyright (C) Microsoft Corporation 2005. All rights reserved.

projects\Win32\VC9\xerces-all\xerces-all.sln(1): Solution file error MSB5014: File format version is not recognized.  MSBuild can only read solution files between versions 7.0 and 9.0, inclusive.

C:\Miniconda\conda-bld\work\xerces-c-3.1.3>if errorlevel 1 exit 1 

Concerningly the linting hasn't propagated the error code on travis-ci (I'll dig into that), but in the meantime:

/Users/travis/build/conda-forge/staged-recipes/recipes/xerces-c has some lint:
  The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
  The recipe must have some tests.

@pelson
Copy link
Member

pelson commented Mar 25, 2016

Also noticed that the Windows build x64 py35 is taking abnormally long and appears to be timing out:

screen shot 2016-03-25 at 04 49 57

features:
- vc9 # [win and py27]
- vc10 # [win and py34]
- vc14 # [win and py35]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need python as a build requirement then? Not sure how these work without it.

make
make check
make install

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Drop extra newline.

groutr added 2 commits March 25, 2016 20:04
I think in this case they provide the same source in 4 different types of archives.
version: {{ version }}

source:
url: http://mirrors.sonic.net/apache//xerces/c/3/sources/xerces-c-{{version}}.tar.gz
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

set OUTDIR=Win32
)

if %PY3K% == 1 (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are there VC14 projects? If not, I recommend the upgrade path shown in https://github.com/conda/conda-build/wiki/Windows-recipe-patterns#updating-older-sln-files

Actually, just updating the VS2008 solution might be cleanest anyway.

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly conda-forge-admin automated user.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/xerces-c) and found some lint.

Here's what I've got...

For recipes/xerces-c:

  • The recipe must have some tests.

@ocefpaf
Copy link
Member

ocefpaf commented Mar 28, 2016

Also noticed that the Windows build x64 py35 is taking abnormally long and appears to be timing out:

That is still happening. Failing for
Environment: TARGET_ARCH=x86, CONDA_PY=27, PY_CONDITION=python >=2.7,<3
and stuck for
Environment: TARGET_ARCH=x64, CONDA_PY=35, PY_CONDITION=python >=3.5

@groutr
Copy link
Contributor Author

groutr commented Mar 28, 2016

@ocefpaf I'm not sure what is happening there.

@groutr
Copy link
Contributor Author

groutr commented Mar 30, 2016

Could the travis build be restarted?
https://ci.appveyor.com/project/conda-forge/staged-recipes/build/1.0.522/job/w605533g02ao9bp8 is very confusing for me.
I'm also kind of baffled with the error for Python 2.7. I get no msbuild errors when I use my copy of visual studio 2008.

@jakirkham
Copy link
Member

The issue with Travis CI is a linting issue (not a build issue). The recipe needs some tests.

@jakirkham
Copy link
Member

The Windows issue seems to be a complaint about the version of the .sln file provided. Though one of the jobs died or was canceled so will restart, but I expect that failure will return for that one case.

@jakirkham
Copy link
Member

Windows restarted.

@groutr
Copy link
Contributor Author

groutr commented Mar 30, 2016

Can an updated msbuild be put on the build machines? Looks like you can compile your own from source (https://github.com/Microsoft/msbuild)

@jakirkham
Copy link
Member

Interesting idea. I have seen that before. Honestly don't have a good enough Windows dev environment to engage in that project productively. Could we put that in an issue somewhere? Probably on the webpage repo. That way someone with more skill in this area and better tools can take a look at it.

@ocefpaf
Copy link
Member

ocefpaf commented Mar 30, 2016

Can an updated msbuild be put on the build machines?

We can ask/request here. They are usually fast to respond.

@patricksnape
Copy link
Contributor

I believe I've seen this problem before. It has to do with the Windows SDK 7 being installed after Visual Studio 2008 Express. For some reason Windows SDK 7 messes with something so that the vcvars32.bat doesn't correct set the @SET Framework35Version=v3.5 properly and so it reverts back to using msbuild v2.0 which is incorrect. You either need to make sure the msbuild from the .NET framework v3.5 is being used or you need to tell vcvars32.bat to @SET Framework35Version=v3.5.

@ocefpaf
Copy link
Member

ocefpaf commented Mar 30, 2016

@groutr I cancelled AppVeyor due to #194 (comment)

We need to get the other packages out too 😉

@jakirkham
Copy link
Member

Well, I believe there is another issue here. Namely, I think python needs to be a build requirement on Windows, which currently isn't the case with this recipe.

@jakirkham jakirkham mentioned this pull request Apr 22, 2016
@jakirkham
Copy link
Member

Restarted the CIs just to see how this would do. So much has happened in the last month. Some general issues (e.g. VS2008 64-bit support) referenced here are fixed. Might as well see what still remains.

Though there are still a few minor fixes required for this recipe before merging. It would be nice to complete them to get this into a good state and clear it.

@jakirkham
Copy link
Member

Seem to be a lot of Windows failures. Does someone want to take a crack at it or can we just skip Windows and send it to a feedstock? This always can be addressed in the feedstock.

@jakirkham
Copy link
Member

@gillins, I'm pinging you here so that you are aware of this PR to add xerces-c.

@gillins gillins mentioned this pull request Jun 23, 2016
@jakirkham
Copy link
Member

The work on this is continuing in PR ( #849 ).

@msarahan
Copy link
Member

Closing, superseded by #849

@msarahan msarahan closed this Jun 30, 2016
Copy link

@JennPlothow JennPlothow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

8 participants