Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
Intergrate the nativeparser_base to our parsertest project
oBFusCATed:
ollydbg:
What patch executable are you using?
All I've tried crashed badly when used with linux generated patches.
ollydbg:
--- Quote from: oBFusCATed on July 07, 2012, 05:15:56 pm ---ollydbg:
What patch executable are you using?
All I've tried crashed badly when used with linux generated patches.
--- End quote ---
I use the patch command shipped with MSYS.
I always download the MSYS zip file from mingw64 site(some one has maintain a full msys environment which contains everything), see:MSYS-20111123.zip
MortenMacFly:
--- Quote from: ollydbg on July 07, 2012, 05:12:19 pm ---Here it is.
--- End quote ---
Thanks, this works. BTW: I still need to modify it if you don't do the diff from the root of trunk. When you are using a subversion 1.7 working copy, applying a patch only works well from root and then the path's are not correct. However, I could handle this... :P
Just looking at the diff I realised you copied the nativeparser_base into the parser folder. I wouldn't do this. Already now they are out of sync. I think a better solution is to either move nativeparser_base into the "parser" sub-folder or move the project file of parsertest one level up.
Your changes conflict a little with the ones of my working copy, but I can handle. For the record, I have touched in parserthread:
- GetTokenBaseType
- HandleFunction
So once you are touching those, we should sync.
ollydbg:
--- Quote from: MortenMacFly on July 07, 2012, 05:44:32 pm ---
--- Quote from: ollydbg on July 07, 2012, 05:12:19 pm ---Here it is.
--- End quote ---
Thanks, this works. BTW: I still need to modify it if you don't do the diff from the root of trunk. When you are using a subversion 1.7 working copy, applying a patch only works well from root and then the path's are not correct. However, I could handle this... :P
--- End quote ---
Sorry about this, but handling different patches is a problem for me(that's why I start using the git), because I have some other changes to the cb_trunk in my local copy, so it is a mess up when I need to select all the changed files in TortoiseSVN, and generate a diff file. For me, the simplest way is just select a folder like "codecompletion", and generate the diff file. :)
--- Quote ---Just looking at the diff I realised you copied the nativeparser_base into the parser folder. I wouldn't do this. Already now they are out of sync. I think a better solution is to either move nativeparser_base into the "parser" sub-folder or move the project file of parsertest one level up.
--- End quote ---
I suggest move the nativeparer_base to the sub-folder, it is all related to c/c++ parser.
--- Quote ---Your changes conflict a little with the ones of my working copy, but I can handle. For the record, I have touched in parserthread:
- GetTokenBaseType
- HandleFunction
So once you are touching those, we should sync.
--- End quote ---
All my changes were record in my git local clone, so I can safely pull the changes you made, and merge it.
MortenMacFly:
--- Quote from: ollydbg on July 08, 2012, 03:38:01 am ---so it is a mess up when I need to select all the changed files in TortoiseSVN, and generate a diff file. For me, the simplest way is just select a folder like "codecompletion", and generate the diff file. :)
--- End quote ---
If you are using TortoiseSVN IMHO is should be possible even from trunk to only select the files in question. If not, I am using SmartSVN where you have a "flat view", meaning that the files are shown in a big list as if there were not directories from the root folder. Then you can select only the files you want to create a diff from. I am not sure if TortoiseSVN has a similar feature.
--- Quote from: ollydbg on July 08, 2012, 03:38:01 am ---I suggest move the nativeparer_base to the sub-folder, it is all related to c/c++ parser.
--- End quote ---
Fine with me.
--- Quote from: ollydbg on July 08, 2012, 03:38:01 am ---All my changes were record in my git local clone, so I can safely pull the changes you made, and merge it.
--- End quote ---
The are not "ready for production" yet. :-[
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version