Downloads:

2,336

Downloads of v 2.8:

923

Last Update:

4/9/2015

Package Maintainer(s):

Software Author(s):

  • Biicode Innovation
  • S.L.

Tags:

development c c++ cmake biicode

biicode

2.8 | Updated: 4/9/2015

Downloads:

2,336

Downloads of v 2.8:

923

Maintainer(s):

Software Author(s):

  • Biicode Innovation
  • S.L.

biicode 2.8

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Failing Test


Validation Testing Unknown


Verification Testing Failed

Details

To install biicode, run the following command from the command line or from PowerShell:

>

To upgrade biicode, run the following command from the command line or from PowerShell:

>

To uninstall biicode, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade biicode -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade biicode -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure biicode installed
  win_chocolatey:
    name: biicode
    state: present
    version: 2.8
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'biicode' do
  action    :install
  version  '2.8'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: biicode,
    Version: 2.8,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller biicode
{
   Name     = 'biicode'
   Ensure   = 'Present'
   Version  = '2.8'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'biicode':
  provider => 'chocolatey',
  ensure   => '2.8',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install biicode version="2.8" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 4/9/2015.

Description

biicode: A cross-platform C/C++ dependency manager

biicode provides file-based dependency management for C and C++ languages. Just #include what you need
and biicode will download, setup, and build the required libraries.

biicode uses CMake under the hood, which makes easy adding existing projects to the biicode system, everything
in a cross-platform way.

Always wanted the power of pip or maven when dealing with large C/C++ codebases? biicode is the tool for you.


tools\chocolateyInstall.ps1
$packageName = 'biicode'
$installerType = 'exe'
$url = 'https://s3.amazonaws.com/biibinaries/release/2.8/bii-win_2_8.exe' # download url
$silentArgs = '/VERYSILENT'
$validExitCodes = @(0)

Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" "$url" -validExitCodes $validExitCodes


In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
biicode 2.7 231 Friday, March 27, 2015 Approved
biicode 2.4.1 255 Wednesday, February 18, 2015 Approved
biicode 2.1.1 564 Tuesday, January 13, 2015 Approved
biicode 2.0.1 363 Monday, January 5, 2015 Approved

2.8 (7-Apr-2015)

  • Better computation of binary targets, if an executable does not depend on its own block library, it will not be linked
  • Removed automatic creation of cmake_dummy.cpp to avoid problems with header only libraries
  • Removed automatic handling of system deps (math, pthread, winsock), that created problems in new toolchains. Now users directly specify in CMakeLists their libs.
  • ADDBIICODETARGETS() has been superseded by ADDBIITARGETS(), which will admit a biicode version number, this is done to achieve backwards compatibility while introducing new build behavior.
  • Fixed bug of include paths missing in [tests] targets
  • Fixed extra verbose message of warning about full path #includes
  • Optimized performance of ignore.bii for large number of patterns, that was incredibly slow
  • Now published blocks show publisher's user name
  • Security fixes
Discussion for the biicode Package

Ground Rules:

  • This discussion is only about biicode and the biicode package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or biicode, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus