add build for windows #651
Conversation
No I'm sorry. |
|
@wenns can you do it? |
jmecosta
force-pushed
the
feature/windows-build
branch
from
8067d48
to
95cc401
Compare
case drive letters change drive normalize paths also in tests normalize paths also in tests
jmecosta
force-pushed
the
feature/windows-build
branch
from
55c82db
to
02b1083
Compare
|
@guwirth rebase and tests are now passing on windows: artifacts created: https://ci.appveyor.com/project/jorgecosta/sonar-cxx/build/artifacts we should also use badges in the readme to show the build is green: |
|
Appveyour supports deployment of artifact to github, it can even do release for you if you want base on tag. Question here is how to enable the build if you can't access weens repository |
What do you mean with this? Heard also nothing from @wenns for a longer time. So I'm also interested in his opinion how to continue... |
|
@guwirth https://github.com/SonarCommunity is a organization. i am for example in these and i can setup builds for any of the projects in those organizations. we could call it SonarOpenCommunity |
|
Im not opposed to moving the repository into such an organisation. My situation is changed and I cannot participate in further development much, anyway. And I'm grateful to you guys for maintaining this code base. As for the actual transfer: just say what I should do and I will transfer the repo. |
|
@jmecosta it is ok for me to move it to an organization. With the name I'm not sure because Sonar, SonarQube and SonarSource are protected trademarks. Also it depends a little bit if only cox plugin should be in the organization or more? |
|
using sonar as part of a bigger word its perfectly ok, sonar is not trademark of sonarsource, thats the reason they add to change it to SonarQube, however Sonar is still used in SonarQube and there is no problems with it.... SonarOpenCommunity, or SonarCxxCommunity are perfectly fine. Both, i think they can have more than just the cxx plugin for sure, if choosing the first we are stating that anything not related with cxx plugin can be made available if choosing the later we are stating only cxx ecosystem tools will be available. Really depends were we want to go with this, i for first have a couple of plugins that i would not mind having them there. like sonar.msbuild.plugin, sonar.fsharp.pluig, sonar.xaml.plugin. also nuget tasks to support cxx plugin etc. this all organization business is very flexible, you can move those repos when you want and to where you want |
|
I tend to SonarOpenCommunity. |
|
Lets try it then |
|
Its done |
|
Thanks @wenns |
|
@wenns thanks a lot for your cpntribution the last years. It's really a pity that you have no more time for doing this... |
|
@wenns thanks a lot for your advices and for your work on SonarQube C++ community plug-in. |
|
@wenns thank you a lot also for starting this project, and hopefully you can still contribute some time in future. we try to maintain it as possible |
|
Thanks for taking over. It would be a real pity to see this code decay. Keep up good work, guys! |
this add build for windows... current sources are not building on windows...
we need to setup a build in appveyour:
@guwirth can you check if after you create a account in appveyour are you able to setup builds for wenns/cxxplugin?
no additicional configuration is needed after this yml is created. see my account: https://ci.appveyor.com/project/jorgecosta/sonar-cxx