Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 12 07:23

    github-actions[bot] on gh-pages

    deploy: 1f89d622e3755d472232591… (compare)

  • Aug 12 07:21

    mloskot on develop

    ci: replace macOS 10.15 with ma… (compare)

  • Aug 12 07:21
    mloskot closed #717
  • Aug 11 21:44
    striezel commented #667
  • Aug 11 21:42
    striezel commented #717
  • Aug 11 21:40
    striezel synchronize #717
  • Aug 11 19:59
    mloskot closed #667
  • Aug 11 19:59
    mloskot commented #667
  • Aug 11 19:58
    mloskot edited #667
  • Aug 11 19:42
    mloskot commented #717
  • Aug 11 18:28
    striezel commented #717
  • Aug 11 18:27
    striezel commented #717
  • Aug 11 17:17
    striezel commented #717
  • Aug 11 17:15
    striezel synchronize #717
  • Aug 11 17:01
    striezel commented #717
  • Aug 11 16:43
    striezel opened #717
  • Aug 10 20:57

    mclow on boost-1.80.0

    (compare)

  • Aug 10 16:39

    github-actions[bot] on gh-pages

    deploy: 8465d5463168a507fdd16d6… (compare)

  • Aug 10 16:37

    mloskot on develop

    ci: partially replace Ubuntu 18… (compare)

  • Aug 10 16:37
    mloskot closed #716
Mateusz Łoskot
@mloskot
@parthsarthiprasad Here are two hints
  1. How does your compiler is supposed to know where to include the Boost headers from ?
  2. How does your compiler is supposed to know that you are building a code that clearly states is C++11 code, so it requires C++11 compilation mode?
    The compilers don't read docs, unfortunately.
I'm fairly certain that if you solve the 1. and 2. the compilation of that test will pass
parthsarthiprasad
@parthsarthiprasad
ah yeah , it was just linker settings , tsk, thanks
Mateusz Łoskot
@mloskot
Well, to be precise, -I (capital i) is compiler setting necessary before linking phase. Good you've found the way
Mateusz Łoskot
@mloskot
@parthsarthiprasad If you want to reach me more effectively, head to the slack channel. I'm spending time on gitter here less and less
Tony Reix
@trex58
Test pixel_iterator fails on AIX within Boost 1.69. This seems to be due to BigEndian. Is this "gil" code aware of Big/Little Endian ? Do you think it has been fixed with version 1.72 ?
Mateusz Łoskot
@mloskot
@trex58 I'm not aware of any big-endian fixes during last ~2 years (since I started maintaining GIL).
@trex58 See https://lists.boost.org/Archives/boost/2010/09/170446.php
So, unless someone with big-endian machine has been keen in GIL, she must have been shy or kept it a secret :-)
Tony Reix
@trex58
Looking at https://lists.boost.org/Archives/boost/2010/09/170446.php and then, it is exactly my issue. We have worked on it, understanding what is wrong at the end, but still unable to figure out where the root issue exactly is.
I have: Assertion failed: v1 == 6, file ../libs/gil/test/pixel_iterator.cpp, line 137
This appears to be due to: at ../boost/gil/channel.hpp:368 : return ret; and ret=46701 = 0xb66d : d/16 = 13/10 = 1101/2 : 3 last bits: 101/2 = 5 !!!
The expected correct value (as seen on Fedora/x86_64): ret=28086 = 0x6db6 : 6/16 = 6/10 = 0110/2 : 3 last bits: 110/2 = 6 !!!
On AIX, bytes are inverted : b6 6d instead of: 6d b6. However, where is the part of code to be made endianess-aware ??
? gil/bit_aligned_pixel_reference.hpp : bit_range& operator++() { ... } ?
? gil/channel.hpp : struct static_copy_bytes { ... } ?
? gil/channel.hpp : integer_t get() const { ... }
That is unclear.
Tony Reix
@trex58
p1:
AIX: (gdb) p p1
$68 = {static bit_size = 3, static is_mutable = <optimized out>, _bit_range = {_current_byte = 0x110022510 "\266m\333", _bit_offset = 0}}
x 0x110022510 :: 0xb66ddb00
Linux: (gdb) p p1
$21 = {static bit_size = 3, static is_mutable = <optimized out>, _bit_range = {_current_byte = 0x41beb0 "\266", <incomplete sequence \333>, _bit_offset = 0}}
(gdb) x 0x41beb0 :: 0x00db6db6
Mateusz Łoskot
@mloskot
@trex58 since this is getting detailed and this space is quite non-persistent (or at least hard to search through), I'd suggest you to open an issue on GitHub and describe the details there. I'll look when I have a moment
Tony Reix
@trex58
OK. Thanks. I think I have other issues with "gil" dealing with endianess.
Mateusz Łoskot
@mloskot
@trex58 issues qualify for opening Issues.
It does not guarantee a prompt fix, but will at least save all the details (ideally with MWE to useful to reproduce) in the public archive making it accessible for anyone who can deal with it now or in future. Gitter room is volatile. The Slack channel is better (has searchable archive), still not the best place for detailed bug reports
Tony Reix
@trex58
Thanks. I'll open the bug report very soon. Do not hesitate to ask for more data if needed. I'm not a C++ expert at all, and this code is very complex for me.
Mateusz Łoskot
@mloskot
Thanks. I will post any questions as comments to the issue
@trex58 I've taken liberty to add Markdown markup to clearly format code blocks

Assertion failed: v1 == 6, file ../libs/gil/test/pixel_iterator.cpp, line 137

I'm actually glad to see this :-) It means the efforts adding new tests are worthy!

Not long time ago we only had the smoke ones https://github.com/boostorg/gil/tree/develop/test/legacy
@trex58 Okey, I'll try to look into that over the weekend
Nedjima Belgacem
@NEDJIMAbelgacem
Hello everyone
I am Nedjima Belgacem. A student at ESi-Algiers (Algeria). I'm interested in working on Boost.GIL project during this year's Google Summer of Code. I have decent C++ knowledge and worked on hobby graphics projects before (mainly opengl). I will start getting familiar with Boost code base, so I'll be posting questions concerning Boost libraries and GSoC program also. I hope I make good contributions to the community :)
Mateusz Łoskot
@mloskot
@NEDJIMAbelgacem FYI, we've recently opened Slack channel (I prefer that one) https://github.com/boostorg/gil/blob/develop/README.md#community
@NEDJIMAbelgacem I'd suggest you to check answers to GSoC questions other student have been posting to Boost dev mailing list during last 2-3 months (2019/12, 2020/01, 2020/02) - https://lists.boost.org/Archives/boost/
There re also some posts on the GIL lists https://lists.boost.org/boost-gil/
In those answers, you will find lots of pointers and links, what to read, what to think about, how to get started, etc.
Mateusz Łoskot
@mloskot
@NEDJIMAbelgacem Regardung readung the list archives, I mean any GSoC related posts, not just those about GIL . Whatever applies to Boost GSoC, it applies to Boost.GIL GSoC too :)
Nedjima Belgacem
@NEDJIMAbelgacem
@mloskot Thank your for your reply
Sorry for my ignorance, I'm not experienced with Slack, It seems like I have to get an invite to access the channels. Am I wrong somewhere ?
Mateusz Łoskot
@mloskot
If you aim to participate in Boost development, the only obligatory communication channel is the Boost mailing list
You don't have to use any of Gitter, Slack
For GIL specifically, I'd suggest to use the dedicated boost-gil list
Yes, for Slack you need an invite. Do you see the topic line of this room? There should be links
I should have stick one in the README.md
Pull requests are welcome :-)
Nedjima Belgacem
@NEDJIMAbelgacem
Alright thank you I'm invited now
ashishvishal78
@ashishvishal78

hi everyone
I am Ashish Vishal, a student of IIT(BHU).
I am interested in image processing so I want to contribute to BOOST.GIL
project in GSoC 20. I am having a decent knowledge of C++ and image processing.
Below is the link of my codeforces, CodeChef and hackerrank handle on which I have submitted some solutions in c++.
codeforces: https://codeforces.com/profile/ashishvishal78
CodeChef: https://www.codechef.com/users/ashishvishal78
hackerrank: https://www.hackerrank.com/ashishvishal7810

I have recently done a project on image processing in the technical fest (Technex) of IIT(BHU) and was the first runnerup of the event. The project code is uploaded on my Github profile.
Below is the link of my GitHub repo
Github: https://github.com/ashishvishal78/pixelete-2020

Pranam Lashkari
@lpranam
Hello, @ashishvishal78 we have got new GIL channel on slack which would be a more appropriate place for any discussion now onwards as we are slowly shifting there from gitter for GIL channel
ashishvishal78
@ashishvishal78
thanks for inviting me
Mateusz Łoskot
@mloskot
FYI, on cpplang.slack.com, apart from #boost and #boost-gil channels, there is also Boost-wide Google Summer of Code channel. Feel free to join #boost-gsos
You can join cpplang.slack.com via https://cppalliance.org/slack/
Manav-Kumar
@Manav-Kumar
Hello Everyone, i have recently joined this channel, I wanted to participate in GSOC by contributing in this project. I had a descent ides on Image Processing, C++ and wanted to actively contribute in this open source community.
Manav-Kumar
@Manav-Kumar
Can somebody guide me on it.
Mateusz Łoskot
@mloskot
@Chinmay-Manas First things first https://lists.boost.org/Archives/boost/2020/02/248236.php then Boost wiki on GSoC, then GIL README and links there
If you have specific questions, post to Boost (or boost-gil) mailing list
See the README or topic of this room for link to slack channels
Manav-Kumar
@Manav-Kumar
@mloskot, Can you please send me invite link for slack group.
Mateusz Łoskot
@mloskot
Bhavuk kalra
@bhavukkalra
Hello everyone,
can i get an invite to boost.GIL channel.