by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 29 2018 11:10
    iainnicol closed #246
  • Nov 25 2018 13:24
    iainnicol commented #246
  • Nov 25 2018 13:23
    iainnicol commented #246
  • Nov 25 2018 12:51
    haf commented #246
  • Nov 25 2018 12:31
    iainnicol commented #246
  • Nov 25 2018 11:52
    haf commented #246
  • Nov 24 2018 23:36
    iainnicol opened #246
  • Nov 08 2018 17:59
  • Oct 31 2018 22:20
    aldaircruz starred Albacore/albacore
  • Oct 25 2018 12:53
  • Oct 15 2018 18:11
  • Sep 29 2018 22:42
    aldaircruz starred Albacore/albacore
  • Sep 19 2018 07:51
    FlyPythons starred Albacore/albacore
  • Sep 14 2018 11:41
    igorkovalchuk starred Albacore/albacore
  • Sep 04 2018 08:18
    haf closed #245
  • Sep 04 2018 08:18
    haf commented #245
  • Sep 04 2018 08:17
    haf closed #244
  • Sep 04 2018 08:17
    haf commented #244
  • Sep 03 2018 13:02
    LaraUrban opened #245
  • Sep 03 2018 12:09
    LaraUrban opened #244
Henrik Feldt
@haf
OK = correctly configured in asmver, in build, in nugets pack; for the 'current' buildable moniker.
it's principle is a loop: for moniker in [ 'net40'; 'net45'; ... ] do asmver; build; collect artifacts;
After the loop, merge artifacts
Next step; in a declarative manner, you'd declare monikers and each task type would output one task (or node, or ...) for each of its valid configuration instances.
A valid configuration instance would contain the moniker.
So it depends on how you want to go about; loop and make the build script more imperative or solve it in albacore in a declarative fashion that people will help you maintain over time
Glen
@tgp1994
@haf That would make sense that Albacore could/should know what target it's building for. I take it then that this functionality currently isn't implemented into Albacore? I'm way in over my head at this point and have next to no idea what I'm doing when it comes to Albacore/writing rake files, I think I'll have to open a feature request in the hopes that someone more skilled than I will take on the task.
Henrik Feldt
@haf
@tgp1994 You should probably aim for the other variant then, to just create a loop and create a new symbol for each configuration. Like:
%w|net40 net45|.each do |fw|
   build :"build_#{fw}" do ... end
end
Glen
@tgp1994
@haf Sorry for the constant questions, but like I said I'm in way over my head here and do appreciate your help none the less :) I'm setting up a ruby environment on my FreeBSD machine so I don't spam Github/AppVeyor with commits everytime I make a change to the rakefile. I went through the steps to get bundler (gem install bundler, bundle install) but when I run rake, I get an error saying I apparently have version 11.2.2 even though 10.3.2 is required. Googling led me to find out that I have to run bundle exec rake instead, which only runs for a second or two before exiting, with 0 output. Any idea why it won't produce any output?
Glen
@tgp1994
Update: Actually that was a simple fix, I just gem uninstall rake --version {x} for the conflicting versions so I can run rake by its self now. However, I'm running into an issue now that you and another developer were actually discussing: logary/logary#27 basically I get an error saying LoadError: cannot load such file -- semver/semvermissingerror. You mentioned installing gems as root, which is true - I cannot run gem install or gem uninstall without sudo. Should I just be running as root the whole time?
Glen
@tgp1994
Yet again it looks like I've solved one problem and created another: I installed rvm to get a user ruby environment, so sudo isn't needed any longer. I can now run rake by its self, but when I do, it just outputs project.rb:137: warning: key :include is duplicated and overwritten on line 140 then it doesn't do anything else.
Sigh... Sorry, looks like it's working just fine, but I must have a syntax error in the rakefile. At least I can focus on that now :)
Glen
@tgp1994
@haf Ok, hopefully I have a good problem for you this time. I implemented p.target = 'net20' and got it to build the nuget package, although when imported into vs the package is still targeting a later version of .NET: targeting '.NETFramework,Version=v4.0,Profile=Client' when trying to import the package into a project. Nothing exceptionally unusual in the rake output besides lib\net20 not found, removing from nuspec. Any ideas?
Henrik Feldt
@haf
Can you run with DEBUG=true as env var, and give the nuspec generates, as well as the output from your shell when you unzip the nupkg?
@tgp1994
Glen
@tgp1994
@haf How can I best get those files to you?
Henrik Feldt
@haf
gist.github.com I suppose
Glen
@tgp1994
@haf Whew, I've got a ton of debug output for you! Here's everything you requested, hopefully: https://gist.github.com/tgp1994/f53c4211c98bd7f92d4f21d0af26294a
Glen
@tgp1994
I've update the gist, this time adding the nuspec from inside of the nuget package. The difference here is that it's missing the <files> tag.
Glen
@tgp1994
@haf Well I think the base DotNetZip package has actually started working ok. The issue I'm running into again here is that for Android, it requires that the assembly be named DotNetZip even though I had to rename it to DotNetZip.Android so the nuget package isn't overwritten. It's almost like I need to have one nuget package targeting all frameworks? Is this possible in rake?
Glen
@tgp1994
Ok I think I'm really starting to make some headway here. I've renamed the Android and iOS assemblies to match the Zip DLL's info, and I've also added in the SolutionInfo link so they build with the same version. I think I may have this fixed!
Jesper Stemann Andersen
@stemann
Is test_runner able to accept Rake::Task arguments?
Henrik Feldt
@haf
@stemann Yes maybe; I don't use that task_type. It's community maintained
serii833
@serii833
Hi. I need some help. Why do I get NoMethodError: undefined method `test_runner' when I try to use 'test_runner' task?
Henrik Feldt
@haf
@serii833 That task type has been removed, because it was failing unit tests. PRs with working unit tests would be a way to get it back.
Sorry about the inconvenience.
Gleb Chermennov
@chester89
@haf hello. I have somewhat odd question - I have an old version of albacore in my project (1.0.0.-rc2). Having recently updated code to .NET 4.6.1, my rake command no longer works (I think MSBuild is picking up incorrect argument or something). Should I upgrade to 2.x directly?
I remember trying to update about a year or two ago, and I had some issues with new version so I rolled back
Gleb Chermennov
@chester89
@haf also, according to the docs - minimum version of Ruby required for this upgrade is 1.9.3?
Henrik Feldt
@haf
@chester89 v3 is latest. And you'll need ruby > 2 for that. Wiki has more details.