Setting MPLAB include path

Alex_rcpilot · Sep 4, 2005

Hi all.As I've switched from 8051s,I still keep the habbit of creating a group of *.inc files in the project folder for the mainloop.ASM routine to include.But now it seems a little difficult for MPLAB.Coz when I go to the setting window Project>Build Options>Project.I see the items marked 'Assembler Include Path,$(AINDIR):' and'Include Path,$(INCDIT):' in the General tab disabled.I can't find anywhere else to designate the custom folder.Is it impossible for MPLAB?I hate including absolute path in my source code.Could anyone help me with it?Thanks in advance

Jay.slovak · Sep 4, 2005

You don't have to use Absolute path in source code, it works fine with relative as well. But I see you want to completelly avoid this, i have to think about it more...

Joel Rainville · Sep 4, 2005

Alex_rcpilot said:
I still keep the habbit of creating a group of *.inc files in the project folder for the mainloop.ASM routine to include.

If your .inc files are in the project folder, you don't need to specify a custom include path. MPASM's include directive will find them. Simply :

Code:

#include "whatever.inc"

You could also manually add them to your project. They'll be listed in the project's sources tree for you to edit them on a double click. You still need the include directives in your main.asm though.

But this doesn't explain the two disabled inputs in the project's build options. That's what I get too with MPLAB 7.20...

Alex_rcpilot · Sep 4, 2005

Hi guys,I'm back.I just fan a test and found out a possible cause for this problem.I was using a long file name 'Delay Routines.inc'.Maybe this was an invalid path for MPLAB.As soon as I changed it into 'DelayRoutine.inc'.Everything was okay!

Jay and Joel,thank you for the replies.

Joel Rainville · Sep 4, 2005

Spaces in filenames is sin! Not using quotes around long filenames is pure evil! :evil:

Light a candle at church next saturday

Alex_rcpilot · Sep 5, 2005

Joel Rainville said:
Spaces in filenames is sin! Not using quotes around long filenames is pure evil! :evil:

Light a candle at church next saturday

I believe it's the evil inheritance ofPASM.Microchip may need to improve its assembler.I can't even store my project in a 'deep' folder.It make a mess in my HDD.I always spare an entire partition named 'Documents' specially for the system folder 'My Document'.Thus my electronic projects is located at Document partition:\My Documents\Electronics Database\My projects.I creat subfolders and store all my projects respectively inside them.Unlike PIC projects under MPLAB,8051 and AVR projects all turned out working fine with this structure.I have to creat folders for PIC projects under the root path,which makes the file structure ugly.It truely sucks!

Jay.slovak · Sep 5, 2005

I use Linker to overcome 62 character limitation. It works fine with it.

Nigel Goodwin · Sep 5, 2005

As I understand it, MPASM is only a 16 bit application, and doesn't support long filenames.

But the entire 'long' filename system in Windows is just a bodge anyway!, it doesn't really support long filenames at all, at least not under FAT or FAT32, I don't know about NTFS?.

Personally though, I consider it really bad practice to include spaces in filenames, it's a stupid Microsoft idea! (as is filenames not being case sensitive!).

Alex_rcpilot · Sep 5, 2005

I've seen the linker function in MPLAB help,but is it really so convenient to use?

Jay.slovak · Sep 5, 2005

Alex_rcpilot said:
I've seen the linker function in MPLAB help,but is it really so convenient to use?

One word, YES
Linker creates Relative code instead of Absolute, this helps you to move program between procesors with minimal modifications.

Alex_rcpilot · Sep 5, 2005

Nigel Goodwin said:
As I understand it, MPASM is only a 16 bit application, and doesn't support long filenames.

But the entire 'long' filename system in Windows is just a bodge anyway!, it doesn't really support long filenames at all, at least not under FAT or FAT32, I don't know about NTFS?.

Personally though, I consider it really bad practice to include spaces in filenames, it's a stupid Microsoft idea! (as is filenames not being case sensitive!).

Well personally I would prefer the compatibility for long filenames as long as those with spaces.It makes the content clearer at a glance at its name.AVR studio supports long filenames,and I'm happy with it.

But anyway,I will do in Rome as Rome does.Taking precautions is the best way to get on well with this environment,just before I switch to C code developement tool.

Setting MPLAB include path

Alex_rcpilot

Member

Jay.slovak

Active Member

Joel Rainville

New Member

Alex_rcpilot

Member

Joel Rainville

New Member

Alex_rcpilot

Member

Jay.slovak

Active Member

Nigel Goodwin

Super Moderator

Alex_rcpilot

Member

Jay.slovak

Active Member

Alex_rcpilot

Member

Similar threads

Setting MPLAB include path

Member

Active Member

New Member

Member

New Member

Member

Active Member

Super Moderator

Member

Active Member

Member

Similar threads

Privacy & Transparency

Privacy & Transparency