Author Topic: C::B & Uniwin  (Read 27101 times)

Offline Rigel

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: C::B & Uniwin
« Reply #15 on: November 22, 2006, 07:35:39 am »
Here is some kind tutorial to make it work on Windows 5.0 and later:

You will need PuTTY package. You can get it here.

Compiler batch files
Code
@echo off
set SELF=%~n0
set LOGIN=%1
shift
set REMOTE=%1
shift
set SRCDIR=%1
shift

:next
if "%1" == "" goto end
        set PARAMS=%PARAMS% %1
        shift
        goto next
:end

set PARAMS=%PARAMS:\=/%

c:\bin\putty\plink.exe -C -batch -l %LOGIN% %REMOTE% cd %SRCDIR%; %SELF% %PARAMS%

At C::B you need to make copy of "GNU GCC Compiler" and name it "Remote GNU GCC Compiler".
Go to Settings>Compiler and Debugger>Remote GNU GCC Compiler>Other>Advanced and add
Code
$(login) $(remote) $(srcdir)
to each profile after first variable.
At C::B in Build options you need to set custom variables login, remote, srcdir for targets.
« Last Edit: November 22, 2006, 08:26:12 am by Rigel »

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9693
Re: C::B & Uniwin
« Reply #16 on: November 22, 2006, 04:07:06 pm »
Here is some kind tutorial to make it work on Windows 5.0 and later:
Very nice! Thanks! :D ...and luckily it worked. ;-)
I'll now try to do the same and then place an article into the WiKi.
With regards, Morten.

Edit: There it goes: What version of Uniwin are you using? It seems there are two - the (outdated?!) sourceforge.net and a commercial one...?!
« Last Edit: November 22, 2006, 04:11:06 pm by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline Rigel

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: C::B & Uniwin
« Reply #17 on: November 23, 2006, 06:50:22 am »
I was using sf.net's version of uniwin.

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: C::B & Uniwin
« Reply #18 on: December 06, 2006, 01:57:26 pm »
I have updated C::B to work with compilers that expect forward slashes as path separators so it is now much easier to setup Uniwin with C::B.

Full documentation can be found here. Enjoy :).
« Last Edit: December 06, 2006, 02:18:42 pm by mandrav »
Be patient!
This bug will be fixed soon...

Offline Rigel

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: C::B & Uniwin
« Reply #19 on: December 06, 2006, 02:15:58 pm »
Thanks alot =)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9693
Re: C::B & Uniwin
« Reply #20 on: December 06, 2006, 02:41:54 pm »
I have updated C::B to work with compilers that expect forward slashes as path separators so it is now much easier to setup Uniwin with C::B.
That is sooooo great! :D I struggled around with the setup but actually were facing exactly this problem. I was wondering anyway how somebody already could use uniwin...?! Nice stuff... will try immediately because this could be really of help at work...
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: C::B & Uniwin
« Reply #21 on: December 07, 2006, 11:38:20 am »
Another update, regarding debugging through Uniwin.

The good news is that it works :).
The bad news is that a small patch is needed for Uniwin's proxy gdb.exe.
Attached to this message you can find the patched gdb.exe which you should copy in Uniwin's folder, replacing the existing one. And you also need C::B revision 3350 and up ;).

[attachment deleted by admin]
Be patient!
This bug will be fixed soon...

wbest116

  • Guest
Re: C::B & Uniwin
« Reply #22 on: January 02, 2007, 01:13:04 pm »
Thanks for update about forward slashes, but I have confused yet because of mismatch of correted file.

For example...

If I modify a file "test.cpp" and save modified file in C::B then "test.cpp" is removed in linux because I set Uniwin's option "Operations on deleting" to "always deleted".

but "not delete" option gives occation to remain "test.cpp.backup" in linux and "test.cpp" does not exist.

Here is the Uniwin's log:
  File Name Changed:C:/work/test.cpp to: C:/work/test.cpp.backup
    => mv /home/test.cpp /home/test.cpp.backup
  File Name Changed:C:/work/test.cpp.cbTemp to: C:/work/test.cpp
    => mv /home/test.cpp.cbTemp /home/test.cpp
  local: C:/work/test.cpp
            ==>  remote:  /home/test.cpp
  File Removed: C:/work/test.cpp.backup
            ==> rm -fr /home/test.cpp.backup

Here is the Linux's .bash_history:
  mv "/home/test.cpp" "/home/test.cpp.backup"
  mv "/home/test.cpp.cbTemp" "/home/test.cpp"

More confused is mismatch result with two logs.

It is not for use gdb.exe just for modify a file which does not pass by compile course.

Thanks.
« Last Edit: January 03, 2007, 01:02:27 am by wbest116 »

tfoell

  • Guest
Re: C::B & Uniwin
« Reply #23 on: March 17, 2008, 10:36:20 am »
I will use uniwin for a new project.
CodeBlocks run under winxp and i will debug/compile on a ubuntu machine.
1. Uniwin is running ! Test button for ssh and sftp is working.
2. But if i change a file on the winxp via CodeBlocks this file is renamed on the remote ubuntu from main.c to main.c.backup ???????
If i use Visual Studion instead of CodeBlocks it seem to work !

But i will use CodeBlocks !
Any Idea ?

3. Is there another way to do remote debugging ?

tobias

seanhoo

  • Guest
Re: C::B & Uniwin
« Reply #24 on: April 29, 2009, 05:25:05 pm »
I will use uniwin for a new project.
CodeBlocks run under winxp and i will debug/compile on a ubuntu machine.
1. Uniwin is running ! Test button for ssh and sftp is working.
2. But if i change a file on the winxp via CodeBlocks this file is renamed on the remote ubuntu from main.c to main.c.backup ???????
If i use Visual Studion instead of CodeBlocks it seem to work !

But i will use CodeBlocks !
Any Idea ?

3. Is there another way to do remote debugging ?


tobias



no answer YET?

Offline ZooLoo

  • Single posting newcomer
  • *
  • Posts: 8
Re: C::B & Uniwin
« Reply #25 on: April 19, 2011, 09:19:54 am »
Hi

I'm using private key to logon the remote host (putty ppk file).
The question is what to do with all the stuff in this case?

Uniwin doesn't have settings to setup the private key file instead of "login/password"
Here is always place for Ы.

Offline Rigel

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: C::B & Uniwin
« Reply #26 on: April 23, 2011, 10:20:18 am »
Hi

I'm using private key to logon the remote host (putty ppk file).
The question is what to do with all the stuff in this case?

Uniwin doesn't have settings to setup the private key file instead of "login/password"
Just load *.ppk into your pagent

Offline ZooLoo

  • Single posting newcomer
  • *
  • Posts: 8
Re: C::B & Uniwin
« Reply #27 on: April 23, 2011, 01:18:14 pm »
Thaks Rigel I'll try this...
Here is always place for Ы.