Searching \ for '[PIC]: MPLAB version control?' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/languages.htm?key=mplab
Search entire site for: 'MPLAB version control?'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: MPLAB version control?'
2003\02\25@114656 by Harold Hallikainen

picon face
    What are people using for version control on MPLAB? With MPLAB prior to version 6, when making a change in my code, I'd copy everything over to a new directory that was based on the date, then modify the prj file to point to the new directory (it'd be nice if source file path references were relative instead of absolute, then no changes would be required). With MPLAB 6, it doesn't look like the project files themselves can be modified like this. Instead, I'm copying the source files over and defining a new project. One project has a lot of C files, and it's a pain to define a new project with all of them. So, what are the rest of you doing?

Thanks!

Harold




________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit http://www.juno.com

--
http://www.piclist.com hint: To leave the PICList
spam_OUTpiclist-unsubscribe-requestTakeThisOuTspammitvma.mit.edu>

2003\02\25@121939 by Ned Konz

flavicon
face
On Tuesday 25 February 2003 08:46 am, Harold Hallikainen wrote:
>      What are people using for version control on MPLAB? With MPLAB
> prior to version 6, when making a change in my code, I'd copy
> everything over to a new directory that was based on the date, then
> modify the prj file to point to the new directory (it'd be nice if
> source file path references were relative instead of absolute, then
> no changes would be required). With MPLAB 6, it doesn't look like
> the project files themselves can be modified like this. Instead,
> I'm copying the source files over and defining a new project. One
> project has a lot of C files, and it's a pain to define a new
> project with all of them. So, what are the rest of you doing?

I use CVS. I run a CVS server on my Linux machine for stability,
storing the files there. Then I run WinCVS on the Windows virtual
machine (I use VMWare to run Windows 2000 when I have to, like for
MPLAB).

--
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE

--
http://www.piclist.com hint: To leave the PICList
.....piclist-unsubscribe-requestKILLspamspam@spam@mitvma.mit.edu>

2003\02\25@125200 by Ned Konz

flavicon
face
On Tuesday 25 February 2003 08:46 am, Harold Hallikainen wrote:
> then modify the prj file to point to the new directory (it'd be
> nice if source file path references were relative instead of
> absolute, then no changes would be required). With MPLAB 6, it
> doesn't look like the project files themselves can be modified like
> this.

Actually, I suspect they can be changed, with care. They seem to be
memory dumps, and the file names are in fixed-size buffers (of
course, they're in UTF-16, since Windows/NT uses Unicode for
filenames.

You could just write over them, doing a "search and replace" for the
old values and writing the new ones. Here's a "strings" dump (looking
for wide characters, of course) with offsets into one of my project
files:

$ strings -t d -e l sample.mcw
  1024 Root Entry
  1152 ComponentManager
  1280 ConfigMemory
  1408 LoadedDisplays
  2052 PIC18F452
  2092 C:\Program Files\MPLAB IDE\MCHIP_Tools\EXAMPLE\TUT452.COD
  2884 C:\Program Files\MPLAB IDE\MCHIP_Tools\EXAMPLE\TUT452.ASM
  3072 OpenFiles
  3200 Debugger
  3328 DebugTool1
  3456 Debugger
  3992 C:\Program Files\MPL
  4096 TempICD
  4224 ProjectMgr
  4352 ProjectMgr
  4480 ProjectDisplay
  5128 C:\Program Files\MPLAB IDE\MCHIP_Tools\EXAMPLE\sample.mcp
 22016 ProjectDisplay
 22144 Configuration Bits
 22272 File Registers
 22400 Watch
 22528 Program Memory
 22656 Watch General
 22784 Watch 1
 22912 Program Memory General
 23168 AB IDE\MCHIP_Tools\EXAMPLE\TUT452.ASM
 24064 C:\Program Files\MPLAB IDE\MCHIP_Tools\EXAMPLE\TUT452.ASM

The strings are terminated by \x00\x00, which makes sense.

So my guess is that you could overwrite the strings at 2092, 2884,
5128, and 24064 with new ones and move the project.

Perhaps I'll make a little program to do this. Anyone interested? Is
Ruby OK? Perl?

--
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestspamKILLspammitvma.mit.edu>

2003\02\25@135440 by 8859-9?B?1m1lciBZYWxo/Q==?=

For version control with MPLAB C18 I use one directory for development,
and create backup directories.  When I need to restore, I copy from the
backup directory to development directory.  Like the following:

C:\Projects\Alarm\Dev\

In here is the project and everything.  And copy everything under that
directory to the backup directories:

C:\Projects\Alarm\030205 - Backup\
C:\Projects\Alarm\030205 - Released 1.0\
C:\Projects\Alarm\030212 - Backup\
C:\Projects\Alarm\030223 - Backup\
C:\Projects\Alarm\030225 - Released 1.1\

Etc.

When I need to restore, I copy the whole directory back to the dev
directory.  This works just fine for me.

Note that by keeping the directory names like yymmdd and put
descriptions like backup, released, I can go back to any saved backup,
by just copying that directory to the C:\Projects\Alarm\Dev\ directory.

Hope this helps...

Omer


{Original Message removed}

2003\02\25@140109 by Lawrence Lile

flavicon
face
I have a simple version control scheme.  In the comments at the top of my
file, I keep revision notes with dates:

Revision
88      Lile     Jan 1 1980     Removed yet another bug

Every so often when I decide I have made enough of a revision, I save by
C file under a new name with a VXX tacked onto the end, for Version XX. So
I would save toaster.c under toasterV88.c, then return to my original C
source and continue to program.   I dont see why this would not work under
MPLAB 6.



-- Lawrence Lile





Harold Hallikainen <.....haroldhallikainenKILLspamspam.....JUNO.COM>
Sent by: pic microcontroller discussion list <EraseMEPICLISTspam_OUTspamTakeThisOuTMITVMA.MIT.EDU>
02/25/2003 10:46 AM
Please respond to pic microcontroller discussion list


       To:     PICLISTspamspam_OUTMITVMA.MIT.EDU
       cc:
       Subject:        [PIC]: MPLAB version control?


    What are people using for version control on MPLAB? With MPLAB prior
to version 6, when making a change in my code, I'd copy everything over to
a new directory that was based on the date, then modify the prj file to
point to the new directory (it'd be nice if source file path references
were relative instead of absolute, then no changes would be required).
With MPLAB 6, it doesn't look like the project files themselves can be
modified like this. Instead, I'm copying the source files over and
defining a new project. One project has a lot of C files, and it's a pain
to define a new project with all of them. So, what are the rest of you
doing?

Thanks!

Harold




________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit http://www.juno.com

--
http://www.piclist.com hint: To leave the PICList
@spam@piclist-unsubscribe-requestKILLspamspammitvma.mit.edu



--
http://www.piclist.com hint: To leave the PICList
KILLspampiclist-unsubscribe-requestKILLspamspammitvma.mit.edu>

2003\02\25@223840 by Harold Hallikainen

picon face
Thanks Lawrence! Since some of my projects have LOTS of files, I'm currently copying everything to a directory whose name represents the date, then continuing on in my "current code" directory. However, since it appears MPLAB (of whatever version) uses absolute paths to files, I have to copy stuff back to my current code directory if I want to burn a chip with the older revision. On smaller projects, I've just created a new project in a new directory, copying over the few source files. But, when there are a lot, I often miss something and spend a bunch of time figuring that out instead of doing something useful.

Harold
---------- Lawrence Lile <RemoveMEllileTakeThisOuTspamSALTONUSA.COM> writes:



I have a simple version control scheme.  In the comments at the top of my
file, I keep revision notes with dates:

Revision
88      Lile     Jan 1 1980     Removed yet another bug

Every so often when I decide I have made enough of a revision, I save by
C file under a new name with a VXX tacked onto the end, for Version XX. So
I would save toaster.c under toasterV88.c, then return to my original C
source and continue to program.   I dont see why this would not work under
MPLAB 6.



-- Lawrence Lile





Harold Hallikainen <spamBeGoneharoldhallikainenspamBeGonespamJUNO.COM>
Sent by: pic microcontroller discussion list <TakeThisOuTPICLISTEraseMEspamspam_OUTMITVMA.MIT.EDU>
02/25/2003 10:46 AM
Please respond to pic microcontroller discussion list


       To:     RemoveMEPICLISTspamTakeThisOuTMITVMA.MIT.EDU
       cc:
       Subject:        [PIC]: MPLAB version control?


    What are people using for version control on MPLAB? With MPLAB prior
to version 6, when making a change in my code, I'd copy everything over to
a new directory that was based on the date, then modify the prj file to
point to the new directory (it'd be nice if source file path references
were relative instead of absolute, then no changes would be required).
With MPLAB 6, it doesn't look like the project files themselves can be
modified like this. Instead, I'm copying the source files over and
defining a new project. One project has a lot of C files, and it's a pain
to define a new project with all of them. So, what are the rest of you
doing?

Thanks!

Harold




________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit http://www.juno.com

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestEraseMEspam.....mitvma.mit.edu



--
http://www.piclist.com hint: To leave the PICList
EraseMEpiclist-unsubscribe-requestspammitvma.mit.edu





________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit http://www.juno.com

--
http://www.piclist.com hint: To leave the PICList
RemoveMEpiclist-unsubscribe-requestEraseMEspamEraseMEmitvma.mit.edu>

2003\02\25@224108 by Harold Hallikainen

picon face
Thanks, Omer. That's pretty much what I do now. If paths were relative, we wouldn't have to copy back to the development directory...

Harold
---------- Vmer Yalh} <RemoveMEoyalhispam_OUTspamKILLspamTEKSAN.COM.TR> writes:

For version control with MPLAB C18 I use one directory for development,
and create backup directories.  When I need to restore, I copy from the
backup directory to development directory.  Like the following:

C:\Projects\Alarm\Dev\

In here is the project and everything.  And copy everything under that
directory to the backup directories:

C:\Projects\Alarm\030205 - Backup\
C:\Projects\Alarm\030205 - Released 1.0\
C:\Projects\Alarm\030212 - Backup\
C:\Projects\Alarm\030223 - Backup\
C:\Projects\Alarm\030225 - Released 1.1\

Etc.

When I need to restore, I copy the whole directory back to the dev
directory.  This works just fine for me.

Note that by keeping the directory names like yymmdd and put
descriptions like backup, released, I can go back to any saved backup,
by just copying that directory to the C:\Projects\Alarm\Dev\ directory.

Hope this helps...

Omer


{Original Message removed}

2003\02\25@224508 by Harold Hallikainen

picon face
Wow! Thanks for the analysis. Can anyone think of a good reason MPLAB doesn't store paths as relative, or let you decide how to do it?

Harold


---------- Ned Konz <RemoveMEnedTakeThisOuTspamspamBIKE-NOMAD.COM> writes:


Actually, I suspect they can be changed, with care. They seem to be
memory dumps, and the file names are in fixed-size buffers (of
course, they're in UTF-16, since Windows/NT uses Unicode for
filenames.

You could just write over them, doing a "search and replace" for the
old values and writing the new ones. Here's a "strings" dump (looking
for wide characters, of course) with offsets into one of my project
files:

$ strings -t d -e l sample.mcw
  1024 Root Entry
  1152 ComponentManager
  1280 ConfigMemory
  1408 LoadedDisplays
  2052 PIC18F452
  2092 C:\Program Files\MPLAB IDE\MCHIP_Tools\EXAMPLE\TUT452.COD
  2884 C:\Program Files\MPLAB IDE\MCHIP_Tools\EXAMPLE\TUT452.ASM
  3072 OpenFiles
  3200 Debugger
  3328 DebugTool1
  3456 Debugger
  3992 C:\Program Files\MPL
  4096 TempICD
  4224 ProjectMgr
  4352 ProjectMgr
  4480 ProjectDisplay
  5128 C:\Program Files\MPLAB IDE\MCHIP_Tools\EXAMPLE\sample.mcp
 22016 ProjectDisplay
 22144 Configuration Bits
 22272 File Registers
 22400 Watch
 22528 Program Memory
 22656 Watch General
 22784 Watch 1
 22912 Program Memory General
 23168 AB IDE\MCHIP_Tools\EXAMPLE\TUT452.ASM
 24064 C:\Program Files\MPLAB IDE\MCHIP_Tools\EXAMPLE\TUT452.ASM

The strings are terminated by \x00\x00, which makes sense.

So my guess is that you could overwrite the strings at 2092, 2884,
5128, and 24064 with new ones and move the project.

Perhaps I'll make a little program to do this. Anyone interested? Is
Ruby OK? Perl?

--
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE

--
http://www.piclist.com hint: To leave the PICList
EraseMEpiclist-unsubscribe-requestspamspamspamBeGonemitvma.mit.edu





________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit http://www.juno.com

--
http://www.piclist.com hint: To leave the PICList
RemoveMEpiclist-unsubscribe-requestKILLspamspammitvma.mit.edu>

2003\02\26@005604 by Ned Konz

flavicon
face
On Tuesday 25 February 2003 07:43 pm, Harold Hallikainen wrote:
> Wow! Thanks for the analysis. Can anyone think of a good reason
> MPLAB doesn't store paths as relative, or let you decide how to do
> it?

Some guesses, having been a programmer for a commercial software
company:

* Lazy programmers. This is usually the case when you see a binary
file that looks like a memory dump. Such files are rarely portable
from one version to the next of a product without extra work. Effort
saved now will be extra effort later -- for someone else, you hope.

* No requirement for relative paths. "Hmm.. you mean you want to move
files??"

* No interest in making an open config format, perhaps because you
could do something interesting with it (like make it easy to use
their competitors' compilers (CCS, for instance)).

{Quote hidden}

--
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


'[PIC]: MPLAB version control?'
2003\06\11@133132 by Larry G. Nelson Sr.
picon face
I do this too but another tool I use is my CD burner. I use CD-R disks and
that way I can roll back a session to recover an older version if needed.
That way I am also covered if my system goes down.

Larry


At 08:53 PM 2/25/03 +0200, you wrote:
{Quote hidden}

>{Original Message removed}

More... (looser matching)
- Last day of these posts
- In 2003 , 2004 only
- Today
- New search...