build-system

I have been struggling with versioning software for a while now. I'm not talking about a naming convention, I'm talking about how to actually apply a version in a build system all the way through to a release. I generally use major.minor.maintenance-[release type] i.e. 1.0.2-rc1 The problem is managing the version number. I've tried many ways (sticking it in a build file, a properties file, a database, etc,etc) but I haven't found anything that really works well. The closest thing I came up with is using Jira which I documented here: http://blog.sysbliss.com/uncategorized/release-management

I am looking for a high-level build system/tool that can help organise my embedded C project into "modules" and "components". Note that these two terms are highly subjective so my definitions are given below. A module is a cohesive collection of c and h files but with only one public h file that is visible to other modules. A component (or a layer) on the other hand is a collection of modules (e.g. Application layer, Library layer, Driver layer, RTOS layer etc.). The build system/tool should - Prevent cyclic dependencies between components and modules (cyclic dependencies inside modules is

I am using the gulp-notify plugin. This is an example of how I'm implementing it in a gulpfile.js ( You can see I'm using gutil and livereload as well. I don't know if they play any factors, but let me know if they do.) gulp.task('js', function() { return gulp.src('./dev/scripts/*.coffee') .pipe(coffee({bare: true}).on('error', gutil.log)) .pipe( gulp.dest('./build/js')) .pipe(notify('Coffeescript compile successful')) .pipe(livereload(server)); }); This plugin works on OS X and Linux. On Windows, which doesn't have a notification feature, it returns an error and breaks the gulp-watch plugin.

I'm new to Sublime Text so am unfamiliar with its internals so far. From what I could tell the problem could be something related to this . I have a python script var = raw_input("Enter something: ") print "You entered ", var which asks for input, waits for it, then prints it out in windows console prompt. How do I make ST3 upon "building" to show the results in a console window? It's really simple just issue a command to start a new cmd.exe . start cmd /K python main.py See here for more(ancient) The /k flag "pipes" the other commands to cmd.exe and runs until you exit the shell yourself,

I am working on a project which takes considerable time to build (10-15) minutes. I have recompiled to verify if there is a compilation error. Now I want to change the install directory so that I have a new version of executable with the new changes. Is there a method to just modify the install path so that the 'make install' installs to a new location rather than the old one? CMake generated makefiles support the DESTDIR coding convention for makefiles. Thus you can override the default installation location by setting the DESTDIR variable upon invoking make: $ make install DESTDIR=/opt/local

I am trying to move to the new build system when compiling with Xcode 10. However, it gives following error: Cycle details: → Target 'project' : LinkStoryboards Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard' Target 'project' : ValidateEmbeddedBinary /Users/project/Xcode/DerivedData/project-hgqvaddkhmzxfkaycbicisabeakv/Build/Products/Debug-iphoneos/project.app/PlugIns/stickers.appex Target 'project' has process command with input '/Users/project/Resources/Info.plist' Target 'project' has compile command