ISSUE SOLVED via COMMENT BELOW this ENTRY

to see how I got there read on

Yesterday:  I Cloned Lapp, renamed to Odoo-lapp.  Briefly changed the line

include $(FAB_PATH)/common/mk/turnkey/lapp.mk

to:

include $(FAB_PATH)/common/mk/turnkey/odoo-lapp.mk

(Changed it back shortly thereafter but after my Pull to the Turnkey Directory.  When I repulled to the Root version directory I verified the change and assumed all was good.  It was not.  This caused my error in that I changed it back but did not pull to the correct directory as was following 2 sets of instructions and had 2 sets of code in TKLDEV)

Today:

ran tkldev-setup

 Ran Make

Error Reads:

Makefile:4: /turnkey/fab/common/mk/turnkey/odoo-lapp.mk:  No such file or directory

make: *** No rule to make target '/turnkey/fab/common/mk/turnkey/odoo-lapp.mk".

Stop

----------

It noticed after TKLDEV-SETUP that a Core folder had been brought in.  I did not Clone it myself.

Changed to Folder Core (from odoo-lapp which is parrallel)

Ran MAKE on CORE:  ran successfully.

------------

Since My Odoo-Lapp does not install however (cloned, renamed but otherwise unchanged LAPP) ???

Perhaps since I changed the name of Lapp to Odoo-Lapp perhaps I need to help new folders withthat name be created that are not crated by the General Make Process.

If I had this still be Lapp, would it run by itself?

I am missing something.

-----------

Postscripts Below 

-----------

1:  potential issue: proceeding but  can I not run this from a OVF Built system?  You reference OVZ problems here:

http://www.turnkeylinux.org/forum/support/20140824/trying-install-minecraft-turnkey-server

that Core make is working it would seem the system is operating so red flag.

-----------------

2: TKLDEV-SETUP:  Yesterday at TKLDEV installation, this didn't jump out of the blog instructions I was following in the blog post (Docs are good) but

https://github.com/turnkeylinux-apps/tkldev/blob/master/docs/setup.rst

./tkldev-setup

B. Setup the build dependencies

In the next version of TKLDev, you can skip this step because it happens automatically on first boot.

If it doesn't (e.g., we didn't have a working Internet connection) you'll be able to trigger it by running this command inside TKLDev as root:

But you're not using the next version of TKLDev (yet), so you'll want to download the new tkldev-setup from GitHub:

cd /usr/local/sbin
wget https://raw.githubusercontent.com/turnkeylinux-apps/tkldev/master/overlay/usr/local/sbin/tkldev-setup
chmod +x tkldev-setup

./tkldev-setup

Do the "Manual Installs" also need to be done after /tkldev-setup ?  They appear to have been built w/ tkldev-setup

The build dependencies: what are they?

1. bootstrap in /turnkey/fab/bootstraps: contains minimal bootstrap filesystems.
2. cdroots in /turnkey/fab/cdroots: contains the cdroot template for the built ISO.
3. common in /turnkey/fab/common: contains source code shared amongst all TurnKey systems.

It appears this was all built in TKL-Dev-setup command

That Core built it would appear all is OK for the system.  

I will look at Pulling Lapp in by itself and seeing if it will Make by itself.  Then it will for sure be something w/ the Name Change I gave yesterday, from your docs/blog post:

---------------------

(My PROBLEM was not navigating to /turnkey/fab/products/new-app-name folder before running these commands.  Therefore dropped separate file set into Root/new-app-name

However, I also followed the GitHub docs and did pull the folder there - just had a test error in the MakeFile which is explained in the comment below)

git clone https://github.com/turnkeylinux-apps/<base-appliance-name>.git
mv <base-appliance-name> <new-appliance-name>
cd <new-appliance-name>
rm -rf .git
git-init