Distribution files need to be placed in their own directory #264

Open
ricklon opened this Issue Aug 18, 2012 · 2 comments

Comments

Projects
None yet
2 participants
Owner

ricklon commented Aug 18, 2012

Currently, these files are placed in a directory that is tracked by revision control. These need to be placed in their own directory. These are the *.dmg, and *.zip etc files that are outputs of the ant dist, and ant dist-test

Owner

ricklon commented Aug 22, 2012

AVR specific code won't run under Chipkit.

Also, libraries should be installed in the user sketch/library folder.

--Rick

On Wednesday, August 22, 2012, bstott wrote:

I've just connected a Max32 to the mpide 023 compatible. I am building a
RepRap 3D printer and was reviewing the ChipKit as a replacement for the
Arduino Mega 2560. I opened the firmware required for running the 4-axis
printer and tried to verify. The mpide doesn't recognise locations of *.h
files under the avr directory - I get an error that the directory for an
#include of "util" does not exist. Does a fix exist? And does it require I
learn the programming?


Reply to this email directly or view it on GitHubhttps://github.com/chipKIT32/chipKIT32-MAX/issues/264#issuecomment-7914637.

Co-founder
Fair Use Building and Research (FUBAR) Labs
http://fubarlabs.org

bstott commented Aug 22, 2012

Note: AVR is Atmel chips. Atmel is the basis of Arduino.

Hi Rick and Alex,

Warnings ----

You say, "AVR specific code won't run under Chipkit."

Then, how do the declarations on the box and corporate worldwide advertising of, "Arduino-Compatible Prototyping Platform." and the product's bullet point list of features containing the statement: "*Compatible with Arduino system." come into play? And, what does one expect of the adapted MPIDE which, is the Arduino IDE updated/revised for the chipKIT for compatability and use? The MPIDE does work well with my Arduino Mega 2560 for the encluded examples. Your MPIDE has just broken the paths/links to include/library sub-directories. You may want to look at MPIDE documentation for clarity and insight. Please revisit this product line.

Oh - for correspondence - I noted that your company's product is named with two concatenated words - (1) lower case "chip" and (2) uppercase "KIT" - thus "chipKIT." I just got through that from the company marketing and the product's box and product sales identification. I'm sensitive of this since I have been technical sales and marketing during the 90's when this type of naming convention came about. I worked for boxLot.com. :-)

Testing:

Just to re-verify your marketing as compatible WITH AVR - This morning I connected my Arduino Mega 2560, that is an AVR, to your company's altered Arduino IDE, that is MPIDE, and loaded the "Blink" sketch. No problem. The application, MPIDE setup for chipKITs, connected and the application loaded and ran. NO PROBLEM. Then, I disconnected the AVR and connected the PIC (chipKIT MAX32) and changed the the blink time from the default 1000 to 200 microseconds and uploaded the same AVR program to the PIC. It loaded and ran. No Problem.

Now, what is my problem? - My problem is that the MPIDE  is not setup or completed for links/paths to the included libraries sub-directories of the AVR within the distributed application (MPIDE) directories. The results being, when you load a sketch/program that is using includes deep within sub-directories they are not found. That is what I was asking for - That your team which, is marketing these products as Arduino (AVR) compatible, set up the links/paths so that when sketches/applications are compiled the IDE, avrdude, gcc, c++ or ??? compiler can find them and finish a compile to load to the MCU. I can kludge it by finding the files and relocating them (I am not yet a programmer.) but, I've machines to build. ;-) And I'm a month behind schedule for a show.

The example sketch/application/firmware I'm working to compile and run is for a Rostock printer running RepRap Marlin firmware. The link is here: https://github.com/jcrocholl/Marlin/commits/Marlin_v1/  If you load and compile this application within MPIDE (It compiles through the un-altered Arduino IDE flawlessly.) you will work out the link/pathway issue that was broken within your MPIDE.  This helps you to be compatible with the AVR realm. Just having the pathways present and recognized for the compiler will make this product closer to what your company markets and wants.

Am I grumpy? Not really. Just not needing corporate representatives spreading mis-information on their direct competitive products at this time. And neither is your company.

Say a little side information about projects I enjoy and am muddling with: Additive Manufacturing. See this link about Obama's announcement for Ohio last week - http://content.usatoday.com/communities/theoval/post/2012/08/obama-announces-new-project-in-ohio/1#.UDUBSqDhRBE

Cheers,

Brian Stott


From: Ricklon notifications@github.com
To: chipKIT32/chipKIT32-MAX chipKIT32-MAX@noreply.github.com
Cc: bstott bstott2002@yahoo.com
Sent: Wednesday, August 22, 2012 6:12 AM
Subject: Re: [chipKIT32-MAX] Distribution files need to be placed in their own directory (#264)

AVR specific code won't run under Chipkit.

Also, libraries should be installed in the user sketch/library folder.

--Rick

On Wednesday, August 22, 2012, bstott wrote:

I've just connected a Max32 to the mpide 023 compatible. I am building a
RepRap 3D printer and was reviewing the ChipKit as a replacement for the
Arduino Mega 2560. I opened the firmware required for running the 4-axis
printer and tried to verify. The mpide doesn't recognise locations of *.h
files under the avr directory - I get an error that the directory for an
#include of "util" does not exist. Does a fix exist? And does it require I
learn the programming?


Reply to this email directly or view it on GitHubhttps://github.com/chipKIT32/chipKIT32-MAX/issues/264#issuecomment-7914637.

Co-founder
Fair Use Building and Research (FUBAR) Labs
http://fubarlabs.org

Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment