Suppose if you have windows with netneans as C/C++ development IDE and you want to create linux builds from the same source code, and you dont want to do all that cross compilation stuff, but you do have a linux machine (server or pc) here is steps that making changes in makefiles generated from netbeans would help to create a port for linux

1. open MakeFile and comment the following two line

1. #include nbproject/Makefile-impl.mk
2. #include nbproject/Makefile-variables.mk

and add two new lines

1. include nbproject/Makefile-impl-Linux.mk
2. include nbproject/Makefile-variables-Linux.mk

create 3 files under the folder “nbproject” by copying;

cp Makefile-variables.mk Makefile-variables-Linux.mk
cp Makefile-impl.mk Makefile-impl-Linux.mk
cp Makefile-Debug.mk Makefile-Debug-Linux.mk
then open “Makefile-Debug-Linux.mk” and change the following parameters

gcc.exe => gcc
g++.exe => g++
as.exe => as
gfortran.exe => gfortran
CND_PLATFORM=MinGW_1-Windows => CND_PLATFORM=Gcc-Linux
CND_CONF=Debug => CND_CONF=Debug-Linux
replace myappoutfile.exe => myappoutfile.sh
open this file Makefile-variables-Linux.mk and replace all occurence of

1. Windows with Linux
2. MinGW_1 with Gcc

open this file “Makefile-impl-Linux.mk” and change

DEFAULTCONF=Debug => DEFAULTCONF=Debug-Linux

When surviving in IT market everyone would tend to think of Creating a appealing product, Reaching customers & Beating competition. Very few will acknowledge those internal factors such as tuning of employee-employee and employee-management pairs. Most firm focus primarily on marketing and on the backend get their ABC app build by recruits, while this works on less crowded segments where clients don’t have much choice.  I have seen lame products that get sold well due to lack of choice.

Same is not true when market is saturated with similar solutions. Here grave mistake done by management are “We don’t need very good developers, just a USA lead is enough to direct Indian resource“.  And plus they don’t show much inclination to employee retention. For an organization that is already pre-existing  in market and have their prove n marketing department, failure of new product is nothing amazing.

If a company has started the product road-map with well planning and positive signs, what caused their new launch butchered in the market? Well factors are not outside but inside the company

Let us go through this with a Case study: A company C plans to develop his ABC software product over a span couple years. They recruit 5 developers of whom two turns out to be geek minded and others are average. That company is using “F” framework & N APIs + few third party libraries to rapid their development. Meanwhile those 2 geeks have left the organization for better opportunities, but company is relaxed their product is almost ready. After 2 years of continuous work they find some limitations in framework they are using and this leaves product buggy and unusable.

At this point there is nothing they can do because the product is a dependent of that framework which itself is buggy, so they plans to drop further work & support.  At first it seems this was bound to happen but wait if the company would have succeeded in retaining those geeky resource, they would found some fix, that is the difference between an average developer that says “Point P is not supported by framework so we cant do it”, a good developer never gives up and finds a way out.

Most senior developers and leads wont get any hint on what a throat-cut competition is pervading today in software industry. Gone are the days of computer innovation & when that mostly looked as science/geeky niche, rather its a fully commercial market. New organizations would not prefer to develop and fresh product & take pain of selling and maintaining it, reason is simple there are too many options out there. Most startups make money from broker-ship of proprietary and open source mature products. Read the rest of this entry »