FPGA Central

When working with complex project with multiple dependencies in Analog
Devices VDSP, it is necessary to include the project group file into
version control. However, as VDSP automatically updates the time/date
record inside the group file at every session, it causes the annoying
conflicts at version control all the time. Is there a good way to avoid
this type of behavior? We are using SVN.


VLV

Vladimir Vassilevsky <nospam@nowhere.co[email protected]> writes:

> When working with complex project with multiple dependencies in Analog
> Devices VDSP, it is necessary to include the project group file into
> version control. However, as VDSP automatically updates the time/date
> record inside the group file at every session, it causes the annoying
> conflicts at version control all the time. Is there a good way to
> avoid this type of behavior? We are using SVN.

Yes, avoid VDSP and make your own build system.
--
Randy Yates % "Though you ride on the wheels of tomorrow,
Digital Signal Labs % you still wander the fields of your
mailto://[email protected] % sorrow."
http://www.digitalsignallabs.com % '21st Century Man', *Time*, ELO

Randy Yates wrote:
> Vladimir Vassilevsky <[email protected]> writes:
>
>> When working with complex project with multiple dependencies in Analog
>> Devices VDSP, it is necessary to include the project group file into
>> version control. However, as VDSP automatically updates the time/date
>> record inside the group file at every session, it causes the annoying
>> conflicts at version control all the time. Is there a good way to
>> avoid this type of behavior? We are using SVN.
>
> Yes, avoid VDSP and make your own build system.

There are many to choose from. Browse
http://www.google.com/search?q=versi...are+comparison

Jerry
--
Engineering is the art of making what you want from things you can get.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

On Sat, 14 Nov 2009 13:58:40 -0500, Randy Yates wrote:

> Vladimir Vassilevsky <[email protected]> writes:
>
>> When working with complex project with multiple dependencies in Analog
>> Devices VDSP, it is necessary to include the project group file into
>> version control. However, as VDSP automatically updates the time/date
>> record inside the group file at every session, it causes the annoying
>> conflicts at version control all the time. Is there a good way to avoid
>> this type of behavior? We are using SVN.
>
> Yes, avoid VDSP and make your own build system.

This helps to make you immune from the egregious changes that IDE writers
always want to make, it gives you far more control over 3rd-party tools
(for instance if you want to generate signal tables or FPGA images in 'c'
files, or if you want to post-process your hex files), and it lets you
use Make, the Only Sensible Build Tool.

--
www.wescottdesign.com

Tim Wescott <[email protected]> writes:

> On Sat, 14 Nov 2009 13:58:40 -0500, Randy Yates wrote:
>
>> Vladimir Vassilevsky <[email protected]> writes:
>>
>>> When working with complex project with multiple dependencies in Analog
>>> Devices VDSP, it is necessary to include the project group file into
>>> version control. However, as VDSP automatically updates the time/date
>>> record inside the group file at every session, it causes the annoying
>>> conflicts at version control all the time. Is there a good way to avoid
>>> this type of behavior? We are using SVN.
>>
>> Yes, avoid VDSP and make your own build system.
>
> This helps to make you immune from the egregious changes that IDE writers
> always want to make, it gives you far more control over 3rd-party tools
> (for instance if you want to generate signal tables or FPGA images in 'c'
> files, or if you want to post-process your hex files), and it lets you
> use Make, the Only Sensible Build Tool.

Amen, brother!

However, it can be a daunting task. Fortunately I've evolved a system
over the last 10 years that seems to work well across multiple
platforms.
--
Randy Yates % "Maybe one day I'll feel her cold embrace,
Digital Signal Labs % and kiss her interface,
mailto://[email protected] % til then, I'll leave her alone."
http://www.digitalsignallabs.com % 'Yours Truly, 2095', *Time*, ELO

>
>When working with complex project with multiple dependencies in Analog
>Devices VDSP, it is necessary to include the project group file into
>version control. However, as VDSP automatically updates the time/date
>record inside the group file at every session, it causes the annoying
>conflicts at version control all the time. Is there a good way to avoid
>this type of behavior? We are using SVN.
>
>
>VLV
>

I still run into the same issue with another Windows IDE. Fortunately i
my case, it's possible to usually know I didn't change anything important
and hit SVN revert before updating. Or you could figure out what locatio
in the file is changing (hopefully a constant offset, or something obvious
and write a short program to overwrite it with the value from th
conflicting revision. If anything other than the dates are changing, the
you've got a mess. Differencing binary files is outdone in badness only b
differencing undocumented binary files. One other option, never havin
used VDSP personally, *might* be to see if there's a way to import setting
from a more sane format, and just import every time you load the project.
No particularly good solution, as others hinted at...